Yes, but there will be no UI for you to differentiate between BTC and B2X. And trying to spend one of them will result in spending the other unless specific precautions are taken.
So during the bcash fork, the suggestion was to send all coins that were in your Electrum wallet to another wallet under your control (after the fork), then it would be safe to send your old wallets seed to a bcash wallet for bcash coin extraction.
I am guessing that can't be done here for s2x, because if you did, your old pre-fork wallet is now empty of both bitcoin and s2x coins, (as coins have been sent to the new wallet after the s2x fork), the private keys of the old wallet won't contain either bitcoin or s2x coins. As for the coins that were sent to the new wallet (under your control, post-fork), well nothing has changed for these coins, so if you sent them to anyone else other than yourself (in another transaction, eventually), they are still vulnerable to replay and loss of the other chains coins (the coins on the chain you meant to send are still safe as always). Can anyone verify this statement is correct?
Yes, you are correct. Currently there is no way to easily split the coins like with BCH. It's pretty shitty of Jeff Garzik and whoever else is associated with btc1 to avoid optional replay protection. I'll begrudgingly accept the argument that strong replay protection will break wallet compatibility.
But there's no good reason not to add a simple form of optional replay protection (like the 3bit address scheme they had originally merged) unless they simply want to cause maximum chaos and user losses. As it is, people will definitely lose money trying to split their coins.
Electrum should be able to detect the fork because of server disagreement when you attempt to spend, but splitting the forked coins is another matter. I wish I could figure out how to use nLocktime in Electrum via the command line. I have a rough idea of how to construct the transaction, but I'm not comfortable doing the hex encoding myself. Still waiting for some documentation on this.
