That’s a weird way of looking at the situation. The Core team has always worked with consensus in mind. Only supporting things that appear to have wide consensus and little resistance. That principle will be what decides the core team position, even in this case.
A network split is a way for both halves to restore internal consensus in case a consensus for the wider community is impossible. If the community can’t reach a consensus about the fork and a split appears inevitable, I suspect the core team will either release two versions, one for each network, or will itself split in two (with significant overlap), each releasing a version for a different side of the split.
If, however, a community wide consensus forms, then that’s what they’ll support.