I think a hard fork is inevitable. However even a hard fork doesn't mean cross-chain (snapchain <-> hypersnap) casts are segregated. That very much is in the hands of NS, as hypersnap intends to continue relaying across protocols even after hard forking. The question is whether NS wants to allow open protocol-compatible behaviour like this to continue, or whether they will deliberately sabotage the route.
-- {no channel}