I imagine content developers would use the same version consumers are, after all that is their target audience. I'm curious whether they'll keep the built-in latency detector.
The whole point of the latency detector is to empirically detect at runtime the delay between motion sensing and the resulting frame appearing on the screen. It would be pointless if they included it in the dev kit and then removed the functionality from the production model.