It's hard to believe someone with Cryddit's could-be-a-Satoshi level abilities would really not understand the diff between ~100% consensual forks and one predicated on a partially-faked "75%" (with 25% + NotXT spoofs strongly objecting).
I can't imagine the chaotic outcome that you predict. Either BitcoinXT (and/or other 8 MB versions of the software) will secure approval of 75% of the miners, in 6-8 months at most, and then 100% of the miners will switch to it; or it will fail to do so, and any miners that switched to it will promptly switch back. The "fake XT" software is a childish idea; miners are in the game for real money, not for lulz.
But (sorry if I repeat myself) the "fake XT" proposal underscores the silliness of blockchain voting. It is typical of the hacker mindset: a complicated programming hack that is invented in an attempt to avoid the need for personal contacts and political negotiation.
Well, sorry, but that does not work. The size limit issue will be decided by *people*, not computers or algorithms. The only effective way to obtain a consensus on some issue is to discuss it with the relevant *people*; listening to them, trying to understand their worries and goals, finding a proposal that most of them could approve, or at least accept, triyng to convince them to do so, and getting their pledge that they will do so.
Gavin, even without being obviously a political genius, knows how to do that (because of his experience at Google, and with the 2010 and 2013 incidents). That is what he did this time, e.g. getting the Chinese miners to agree to 8 MB. That is apparently an approach that Greg and Adam, prototypical hackers that they are, do not seem capable of doing -- and, for that reason, hate it, and call it "populist tactics".
I bet that the Core × XT "war" will be resolved that way: the miners (the Chinese, and probably others too) will talk to each other, and eventually agree that they all should raise the limit (by downloading BitcoinXT or some other 8 MB version, or rolling their own); or that they all should stick to 1 MB.
By the way, in the BitcoinXT Github repository there is already a branch that has only the 8 MB limit increase, without the other controversial changes:
https://github.com/bitcoinxt/bitcoinxt/tree/only-bigblocks(This is not a recommendation, of course; only an information.)