I not suggesting it should think its secure when its not. Just of ideas to prevent it from popping the eFuse when its not secure (custom roms and such), so that if you revert to a secure system (OE rom) it does not refuse to act secure because of the eFuse reflects that at some time with a previous load it was not secure. Unless the chatter about Knox not working after restoring to a secure state once the eFuse is blown from a previous custom rom are not true I'm under the impression that some apps will not treat the phone as secure if that eFuse is blown, regardless of whether the current install actually is secure.
Maybe I'll just sit back a bit and see how the updates and news concerning this plays out. I like to run custom recovery so that I can do full backup/restores with easy, but if I'm on travel out of the country I would like to use the phone in a much more secure manner, maybe one day even access to work related things if my employer decides to support Samsung's push into corporate market place.