Why does "can OTA add protocols?" never get settled? Because three questions get rolled into one: can it update at all, can it update the protocol chip, and is it allowed to update a private protocol. Take them one at a time and it's clear.
Plain OTA — anyone can do it now: a compatibility fix, a new feature, a protocol toggle. But a toggle is just a switch. That protocol was already in the chip; the maker shipped it turned off, and OTA turns it on. That's enabling, not adding.
Protocol OTA is different. It updates the protocol chip itself, so a device already sold genuinely grows a new protocol — adds AVS, moves UFCS to 2.0. That takes architecture, not a switch.
Licensed OTA is different again, and it has nothing to do with technical ability — it's about permission. A private protocol like Xiaomi's hyper-charge can't be pushed into a product without the owner's license, even when the capability is there. So CoCan can add AVS a year after launch, but won't push a Xiaomi protocol on its own — that's licensing, not capability.