Instead of disabling the check explicitly, the code could (and should) be modified so it doesn't do the check unless it's needed - i.e., CDR_FORCESPEED is not set, -force is not specified, and burnfree is not specified on the command line. As a general rule, hardware shouldn't be relied on to do any more than absolutely necessary, precisely to avoid this kind of problem with nonstandard behavior.
Instead of disabling the check explicitly, the code could (and should) be modified so it doesn't do the check unless it's needed - i.e., CDR_FORCESPEED is not set, -force is not specified, and burnfree is not specified on the command line. As a general rule, hardware shouldn't be relied on to do any more than absolutely necessary, precisely to avoid this kind of problem with nonstandard behavior.