My understanding is that WHATWG doesn't govern standards at all - it basically documents what browsers are doing at the moment. So when Google rolls WEI in a Chrome update, it will become a WHATWG "standard" automatically. Is that correct?
To actually become a standard it needs at least two inependent implementations.
But it's interesting that you wrote what you wrote. Because that's exactly what Chrome is doing: it's announcing an intent to implement, and then enables whatever they intend by default. Oh, they do pretend to ask other vendors about their position, but ship anyway. And then use web.dev to pretend it's a standard.