Noel Borthwick [Cakewalk]
Yes I've tested both bluetooth headsets as well as bluetooth speakers and they work fine. You can even record from a bluetooth headset and use the transport controls on these headsets to control SONAR.
The latency for bluetooth is high so its not useful for input monitoring - you can playback and mix with them however. With WASAPI exclusive you can run at a low buffer size so you can reduce the latency to just the bluetooth latency.

What about KleerNet which has lower latency, longer range and higher quality than Bluetooth? Seems rather underused and unknown by the masses yet.

I ran the loopback test on my other Laptop from work, The results are much better, still off but only by about 4 ms. Notice Shared mode is worse than exclusive still. So I would avoid shared while tracking. 
 

 
 

 
I'm just downloading the latest Splat to my office computer and will try and test Windows 10.   

OK here's the loopback test in Windows 10 using Splats latest download.  
I don't really see much improvement over W7 at all. 
Sure you can mess around with the Manual offset so just be warned about what your dealing with. 
 
 
 

I'm not asking to be a Butt head but I have never got why latency is of any consequence.
I don't have any issue with latency, I have none. 
Why is it to others?  

soens

Noel Borthwick [Cakewalk]
Yes I've tested both bluetooth headsets as well as bluetooth speakers and they work fine. You can even record from a bluetooth headset and use the transport controls on these headsets to control SONAR.
The latency for bluetooth is high so its not useful for input monitoring - you can playback and mix with them however. With WASAPI exclusive you can run at a low buffer size so you can reduce the latency to just the bluetooth latency.

What about KleerNet which has lower latency, longer range and higher quality than Bluetooth? Seems rather underused and unknown by the masses yet.

I don't know much about it but if they have drivers that work in Windows, you should get it for free using WASAPI in theory.

Cactus Music
Sure you can mess around with the Manual offset so just be warned about what your dealing with. 
 

I'm not sure why you say 'mess around'. Manual Offset is specifically intended to address uncompensated input latency.

Cactus Music
Notice Shared mode is worse than exclusive still. So I would avoid shared while tracking. 

As one should anyway.

Sorry, I guess nobody understands what I'm on about here.
I'll leave it be,
I won't be using WASAPI for anything other than editing midi tracks anyhow.  WDM still works better with my Tascam if I'm using more than one interface, which is rare.  WASAPI caused the audio engine to stop with the Tascam, seems each interface will possibly behave differently with this. There's a thread with someone now has issues with their X32 , That's interesting to me.. 
http://forum.cakewalk.com/Wasapi-driver-problem-with-playlst-appeared-in-SONAR-201611-m3522161.aspx
 
 

11Dreams
I'm not asking to be a Butt head but I have never got why latency is of any consequence.
I don't have any issue with latency, I have none. 
Why is it to others?  

Sorry to open an old thread but I thought your question deserves an answer.
 
If all you are doing is recording and playback latency has no impact at all. Who cares if you have to wait a quarter second for the wheels to start rolling? Stability is more important than latency.
 
But if you are using virtual instruments then it is super important. The timing of the performance suffers.  A latency of 20 milliseconds is like having a speaker 20 feet from the player. A 200 millisecond latency is like having your guitar amp 200 feet from you. Sound travels at roughly 1000 feet per second.