Again, power consumption/connection lifecycle isn't directly a competitive advantage because your user doesn't care so long as it works. (Slack and FB Messenger seem to have terrible power consumption and connection lifecycles for mobile but also seem to be doing just fine.)

(Not to mention those are also things that could be fixed in an open standard, if people cared to contribute that effort. The unfortunate reality is that isn't a competitive advantage either.)

The competitive advantage is to find excuses to dismiss open standards, whether the arguments are technically or factually correct is another matter, and build walled gardens.

But more crucially to my previous point, being technically superior isn't really a competitive advantage if a user doesn't notice it and in fact, can slow one from getting first mover advantage by shipping something/anything faster and sooner. I really don't think that on a power consumption or connection lifecycle standpoint any of the closed source protocols are really all that much better, and we have mostly nothing but anecdotes to trade on that question because the companies want to maintain their secret sauces.