I'm aware that both work in different ways. I just don't see any reason why a mic would not be able to offer similar functionality. I can't think of a single good reason why. If you're using the mic, then you're not using the Kinect. They have resources reserved for the Kinect that would dwarf the requirements for processing the audio from the mic. Seems simple enough.
Oh, I'm definitely not saying it will be as good! I've actually made the opposite argument countless times. The headset has to deal with:
There's probably more I'm not thinking of atm too. Having the Kinect is absolutely beneficial. But voice commands via a headset should work, and I think it's likely to be added for those without a Kinect in the future.
- You have to actually wear it.
- You're tethered to a controller.
- It's not going to be turning your system on.
- You were probably already using it for voice chat (this problem exists for Kinect if you were using that for voice chat too though).
- If your controller standby's then you're not saying anything until it's done waking up.
http://semiaccurate.com/2013/09/03/xbox-ones-sound-block-is-much-more-than-audio/
Audio block is literally built to work with the kind of data sent to it by the Kinect.
Here is another huge one for your list:
* Voice commands will not work while the microphone is muted meaning everyone you're talking to will hear you give voice commands.
You can, but not in a very convenient way. All you can do right now is highlight a pin, press the menu button, then select "move to front", which moves that pin to the top right slot, then shuffles all the other pins down/across.
You can also do it with the smartglass app.