My company has bought other companies in the past and inevitably we've had IP space conflicts. Work arounds involved requiring users to connect to different VPNs to use services running in different networks. The end result was that we had to renumber huge chunks of the company and patch up the routing tables to make this work.
If we'd both been running IPv6 there wouldn't have been any IP space collision. We could just connect them together and be done with it.
It also only really works when it's a 1:1 scale, as you add more networks the configuration grows with N^2.
For this to work you need to expose the services to those non-overlapping blocks, ie write DNS views and associated shenanigans.
At this point you are half-way to IPv6, so why bother with implementing NAT44 at all?
The way you structured it, I feel like the analogy for "living on Mars" would have to be "merging company networks", but that happens all the time.
If Mars is supposed to be IPv6 then I can't figure out what the utilities are supposed to represent.
I was making a "joke" that it's as likely as us getting to another planet and it being already setup to be habitable by humans.
In my ISP/cloud provider days sure I spent a lot of time implementing v6. But it's just nowhere near worth the cost to mess with particularly when you still want/need public v4 along side.
Also, I don't understand how v6 could be responsible for these post peak prices. Most everyone still has the v4 addresses as well and no way v6 only cowboys are outpacing general growth.