reading through the replies to this, perhaps it should instead be that if you create a method to prevent downgrades you must also provide documentation on how that prevention method works in great enough detail that it can be circumvented.

Were they to document a way for you to disable the fuse check, then the user could disable the fuse check and do their own downgrades, or if writing this kind of technical documentation is too laborious then they can just provide themselves a downgrade service and just point to that in the documentation.