I understand Data center migration is heavy topic:
If you are looking for easy methods - look at the solutions like Zerto (I'm not promoting this product) which has features like sandbox testing and can carry network stack features.
I'm not AD expert but pretty sure this is a general scenario for most of the customers to extend the AD functionalities to Recovery/Remote/DR sites.
If you are not planning for version change but only Lift & Shift to save the VM's state - think of storage level replication (pre-seed - replicate - final cutover) and failover VM's in waves (assumption all are VM's)
Keeping in mind that both AD1 and AD2 will have the same IP address - Do you mean same IP range or exact same IP value? Also ~3000 kilometers is considered as a remote site (not sure of latency that you have and pipe connectivity)
Having said that - preserving network schema for VM's Vs maintain consistent AD replication between sites seems tricky requirements
As this is consultation work - depending on DC migration tools/companies may through brighter ideas
To conclude - list the individual dependencies like AD replication/VM grouping/Network NAT and list possible options with pros & cons of each method rather than treating this as a whole scenario as a puzzle to break.