1. %90 of the hashpower; Just like BCH, Similar scenario will happen in November. This is technically a hardfork. There will be legacy chain and 2x chain and companies who signed to agreement will switch to 2x. 2x nodes will be rejected by Core regardless what they try to do. Miners mine what is most profitable.
The Bitcoin Cash fork has the Emergency Difficulty Adjustment logic as they knew they were going to be a minority chain. This time neither the Segwit2x fork or the Core fork is going to have anything like this so I don't think there will be any comparison. This is a new experience.
I'm sure we can agree that the fork with the highest hash power will be paying rewards out more frequently. However the unknown quantity here is how much those rewards will be worth in Fiat (say $$) and this will remain unknown until probably right up to the closing days. None of the large exchanges have yet formally confirmed how they'll be handling this fork or if the minority chain (whichever it is) will be tradeable. We might not see this until the hours or the day after the event.
As a final note I know they have bills to pay but a Miner which prefers rewards in Bitcoin over Fiat is always going to command more respect because it shows they have faith in the network they are giving the hash power to.
2. Political Games; Look, we all know that this agreement was never about blocksize. We all know that. You want big blocks? Go BCH you've got 8MB blocks there. You want Segwit? Here you got it. With latest upgrade blocksize is already big enough. They might tell you that this deal is about blocksize but actually it's all about firing the core devs and controlling trillions of money flow.
They said "The only way to get smarter is by playing a smarter opponent." If Core survives it will more hard to take down. If not, I will keep supporting the legacy chain.
Bitcoin is resistant to control and if it wasn't there wouldn't have been so many years of debate, round tables, publicity campaigns and general toxicity. Besides, I don't think "core" is all that centralised anyway and many developers outside of the vocal few don't ultimately care if the blocksize cap is 1Mb or 2Mb.
I don't disagree this is about control but I would suggest it's easier to control a restricted and congested network than it is one with capacity to expand.
You paint a black and white choice between 8Mb blocks and Segwit but this doesn't exist. Some people want to see Segwit implemented and would also like to see 2Mb blocks and that's what happening now.
Segwit was never a blocksize increase. It was a transaction malleability fix with a blocksize benefit and even now weeks after activating the "real" blocksize (inc. witness data) is very rarely making it over 1.1Mb You might want to point out that's with low adoption and you'd be right as that seems to be holding around 7% at the moment but if segwit was the awesome solution "everyone" wanted then why isn't it 50% ? Maybe the rest of the community/network doesn't really care about segwit after all.