Something should be done to make sure the network is unaffected if/when a lot of masternodes go offline simultaneously. Otherwise the network can be attacked any time.
The core developers are already working on this, but since this is a big change on how masternodes handle each other every possible side effect must be considered, and all changes must be very carefully tested before a release.
In other works, it will need a while until it's implemented.
I might be wrong though but what's clear that it's a bad timing to have forking issues.
It's always a bad time to have forking issues :-)
Fortunately most users are not affected by this.