Also note that we're looking at different interest groups.
BCH caters to big-block purists, who don't want segwit at all and have the opinion that on-chain scaling is sufficient. 2X caters to people that do want segwit, yet have the opinion that segwit alone is not sufficient, making an additional blocksize increase necessary. One might also argue that 2X tries to be the unifying proposition by making a compromise between both sides of the blockchain debate, which may be interesting in itself.
BCH caters to big-block purists, who don't want segwit at all and have the opinion that on-chain scaling is sufficient. 2X caters to people that do want segwit, yet have the opinion that segwit alone is not sufficient, making an additional blocksize increase necessary. One might also argue that 2X tries to be the unifying proposition by making a compromise between both sides of the blockchain debate, which may be interesting in itself.
There's a common misconception that this is a debate only about scaling, while actually the major point of disagreement is security. Core is not arguing that bigger blocks, and especially bigger blocks with SegWit would quickly boost Bitcoin's capacity and lower fees for some time, but they believe that this will dramatically reduce number of full nodes, making Bitcoin less decentralized and secure. Small number of full nodes will make Bitcoin weak to government attempts to shut it down as well as different kinds of double-spending attacks.
Ironically both sides claim that the other side's approach is less secure and would endanger decentralization. From what I've read the main arguments by Core against Segwitx2 were less about the blocksize (the increase being less extreme than BCH or unlimited), but rather about the development, testing and deployment approach (eg. little being known about the intricacies of hardforks, too close a deployment date, non-existent or questionable replay-protection). I might be wrong though, maybe even a relatively conservative block increase to a total of 4mb (2mb + 2mb segwit) is already seen as problematic in itself.
