That isn’t a good way to handle replication between two database servers. The problem is better solved by using one master and multiple slave. Allowing slaves to be replicas of the master where appropriate. If the master fails you would promote the slave to be the new master and update DNS and so forth.
Having WordPress manage this kind of info is a recipe for data corruption in terms of split-brain scenarios between your two writable databases that, as far as I can tell, you intend to be replicas in an active-active environment. Furthermore, what if just one insert is missed on one of the systems? Now you have differing auto-increment IDs. which one is the right ID? Both? None?
