While the rationale for making it relaxed is probably valid for external callers, an internal caller[1] is already using it incorrectly. Rather than fixing the internal caller, it seems easier and less bug-prone to just make isReady() do an acquire-load.

[1] That method is only called from its unittest at the moment, so there is no bug in the shipping binaries.