For your own infrastructure, re-using the same addresses over and over, as in a CG-NAT scheme, makes it far easier for mistakes to happen and far harder to diagnose them. Your network becomes a fragile component that your own network engineers are frightened to touch, hurting your ability to compete as a network provider.
What's 10.20.30.40? Your own notes show you use 10.20.30.40 in Sector A of the country for a Cisco router but you also named a different device, a microwave transceiver in Sector B of the country 10.20.30.40 with the NAT supposedly separating the two. So packets supposedly "from" 10.20.30.40 could be the Cisco router playing up again, but they could be that microwave transceiver misbehaving, or they could be CPE leaking a customer's internal addresses into your CG-NAT network. If you try to "solve" this over the network you might end up talking to a "different" 10.20.30.40 than the one causing problems and make things worse.
Once you realise you want IPv6 internally, it's not a huge leap to realise that you might as well at least _offer_ this to customers too.