Core developed, tested and implemented Segwit over a nearly two year period. There was never any agreement among Core developers to back a hard fork block size increase. I think some of them are open to it, but the main problem is the back room dealing and economic coercion characterized by Segwit2x. And the really short timeline. It's prudent to implement hard forks on a 1-2 year timeline give Bitcoin's massive user base. 3 months guarantees a major split if there is much support for the hard fork.
Thank you in advance for your help.
My recollection is that BCH has 8MB blocks (no Segwit). B2X will 8MB blocks (Segwit). Since Segwit is backward compatible / opt-in, it takes time to see the ecosystem upgrade. That's why, presently, less then 10% of network transactions use Segwit. So, out the box, BCH is more useful than Segwit2x if all we're talking about is sheer transaction throughput. Bitcoin Cash has a separate problem of heightened inflation because of changes they made to the difficulty algo, but they're hard forking to remove those changes next month, last I heard.
The fact that BCH is forking again will probably have a big effect on its price. It is currently at an all time low and the fork won't be good for it. With B2X however, I don't see as many people saying "wow, it is so much better" like how people were doing with BCH. For this reason I believe BCH will last longer than B2X and will be considered more valuable. In the long run I expect both of them to collapse.