fd00::/7 (technically fc00::/7 but IIRC the lower half is reserved) is supposed to be used for all local addresses and is equivalent to the private reserved ranges in IPv4.
https://en.wikipedia.org/wiki/Unique_local_address
Getting connections to actually get MADE on the ULA first rather than a global address and to handle firewall rules... now THAT is the actual PITA.
But people like the NAT. I'd guess it's the only part of networking that gives people a warm and nice feeling; it appeals to our senses of ownership and security.
NAT is a thing that creates real problems, for example inhibiting low-latency video calls.
100ms isn't that low, and those NATs are introducing additional latency and complexity that don't need to exist. If both sides are behind NAT then you may well need to relay the connection through a third party server, introducing even more cost, complexity and latency and involving an otherwise-unnecessary third party.
"I managed to get something working" doesn't invalidate any of that.
Network latency added by natting is microseconds.
Imagine I had a public IP - no natting involved. How would my video client tell my stateful firewall to allow a new incoming connection from the calling device?
Once you have to bounce the data through a hosted proxy, you're forcing no less than 10 ms on to the users (of course there are rare exceptions for users really close to your proxy).
The whole point of v6 was no more NAT. The consequence is that a prefix change is a major event.
The original designers imagined the prefix to be eternal. Reality, predictably, turned out to be quite different.
Sure there are ways to deal with this, but it's far from "v4 with more bits".