Well you might as well fork because core is never going to do it.
cores the only one with the Fork threats
What you are describing is what
I and others call a bilaterial hardfork-- where both sides reject the other.
I tried to convince the authors of BIP101 to make their proposal bilateral by requiring the sign bit be set in the version in their blocks (existing nodes require it to be unset). Sadly, the proposals authors were aggressively against this.
The ethereum hardfork was bilateral, probably the only thing they did right--
PoW algo threats
Bip148 mandatory activation fork threat
all the deadlines. all the REKT campaigns..
meanwhile all the other non-core implementations just plod along without making threats and leave it for users to choose openly as they please.
oh and i do laugh.
when a core dev pretends to be independent. yet then screams they refuse and are afraid to do the reviewing of other implementations..
then goes out and screams other implementations are not independently reviewed.
thats like not paying child support then screaming out that its a travesty that children are not supported by deadbeat dads