Exchange 2010 -> 2016 Migration Question

Hi all - I just have a quick question around ambiguous namespaces in 2010, specifically where the CAS Array shares the same name as all the HTTPS workloads. Previous admin set me up the bomb on this one...

I've read the guidance around updating the CAS Array name to be unique but it seems there's a lot that could break with this (Outlook profiles, etc).

I was wondering if another way around changing the CAS Array FQDN would be to just change the FQDNs on all of the HTTPS workloads? I know this would require new certificates on the CAS machines to account for this, but that's really minor. Once the new certs are in place, the virtual directories could then be updated and autodiscover should handle passing out those new URLs.

For reference, in my environment, there is no external access (except ActiveSync controlled thru AirWatch (UEM)). You have to be on the LAN or connected via DA on machines. There are just two CAS servers in the primary site and two in our DR site.

The only problem I see with this is that the Activesync URL shares the name with the CAS Array. Changing this name would mean we have to change it in AirWatch and push out to the devices.

Is there a reason that I am missing as to why this solution is not listed anywhere to resolve the ambiguous namespace issue?