I've read multiple tutorials on IPv6 and it's so complicated that I still can't grasp how it all works in my head. For some context, I've personally written an Ethernet IPv4 network stack with DHCP from scratch. I also worked on Ethernet switch firmware, coincidentally for SpaceX...
Also getting an entire public prefix assigned instead of just a single address is amazing too. On my public servers I let my ssh service listen on a randomly generated static IPv6 address from my prefix, which is not used for anything else. On that same machine I can have dozens of other public services on their own IP each (they can even all run on the same port because they're using different addresses), and when someone then decides to scan the IP of my website for interesting ports, they won't find anything.
To be honest, if someone doesn't understand IPv6, I doubt they really understand IPv4 either. Many issues with IPv6 today come from the fact that everyone and everything is so used to V4 concepts, that most products focus on IPv4 first and then half-ass IPv6 support (if they implement it at all).
Address asignment in an IPv6 world is more complicated - you can do DHCPv6, or your can do stateless auto-config. Which should you choose and when? Many other aspects of the stack require more knowledge.
And THEN you ALSO need to understand how v4 and v6 interacts so you can provide suitable compatibility - the various different methods of tunnelling and negotiation.
In my opinion you shouldn't really bother with compatibility. Just do dual stack and maybe NAT IPv4 if necessary.
For my personal use cases IPv6 just proved to be much more versatile than IPv4. It did take some getting used to since it's approached differently, but learning it is very worth it and also helps using IPv4 better
SLAAC is only a drop in replacement in the (typical) home.
I have seen too many people that have the same excuse. The advise I gave them is to forgot all the things learnt from IPv4 and study IPv6 as a totally new IP stack.
The problem is people look at it from IPv4 view, which is a currently a mess with IPv4 exhaustion.
Most people who would know how to set up port forwarding could probably set it up. I think even some routers support it built in now.
Of course, today IPv6 only can't be considered full internet access, so providers usually need both – and given that CGNAT gets consumers 99% of what they want/are willing to pay for, providers sometimes can't be bothered to also implement IPv6.
I used to have GCNAT + IPv6 on my provider, but the v6 part of their CPE was worse than useless – no option to open ports since "port forwarding is not needed on IPv6" (nevermind the mandatory firewall that doesn't allow inbound traffic unless completely disabled).