Hi Michael,
As far as I'm aware, websockets and the older subscription method result in the exact same data flow. SOAP just isn't involved here for status. It's only used to background sync changes to the device/scene/program list.
What you might be referring to is SOAP vs. REST. We've opted to continue to use the SOAP interface (like the Admin Console) to continue to support the older firmware devices out there.
For speed and status, as soon as we get the first bits of status from the subscription channel we update status as it rolls in. Websockets vs. subscription isn't any faster than what we already have in place as both are socket based.
The bottom line is we won't move to websockets until we see the vast majority of users using firmware that supports websockets and only if there is a performance reason to do so (which currently I don't see).
Wes