You know Carl_Wilson, thinking through this a bit further now... If the driver could simply do a Windows version check at installation (or, at runtime) and dynamically enable or disable based on the patch level... You could essentially do your point release now, with a high degree of confidence that it will be disabled for who it needs to be disabled for, and enabled for who it needs to be enabled for... Right?
Then if down the road MS backports the fix via a KB patch, you could simply do the same thing (another point release) to have it verify that patch is installed before allowing the feature to be visible.
gets you guys COMPLETELY out of the position to be a roadblock. You're driver works, right now. All you are waiting on is RS2 to be released, at which point the driver automatically works as expected with no further work for you guys to do.
Eh, eh, eh...?