For at least some of these environments, the @noLocks annotation is probably more appropriate (with an asterisk about its current incarnation being overzealous), as in many of these use cases you only need such restrictions on critical sections, rather than the whole binary.
It's worth considering, however.