The reason behind HATEOAS was that REST was in practice being watered down from how it was originally envisioned, so proponents of the original vision needed a new term.
I don't think that your origin story being "well we needed a way to tell all the practitioners they were consistently doing it wrong" is a good indicator of potential success.
With all these standards, the successful ones need to find some magic moment to take off - like HTTP did.
Too early to tell if ActivityPub (which I like as a protocol very much) will be an HTTP or an XML.