You don't hear much official response here because it was intended to be used as a user-to-user forum more than a direct line to the developers and such. It's detailed in the sticky welcoming you to this forum.

The vendors have more actively communicated with users though (both AMD and nVidia... unfortunately more so nVidia than AMD)...but that is over at their forums. Which is actually more appropriate, as it is an issue with their drivers not properly interfacing with all of DX9.

Both camps had pretty much written off DX9 about 18 months or so ago. A big chunk of both brands' lines got sloughed off into legacy status. Forget exactly when it was in the AMD line (late 2012 or early 2013 I think), but for nVidia it was around their 340.xx to 343.xx driver releases. There are notes in there where anything pre-400 series has been dropped. So users have to use the older drivers for the proper legacy support (ie: pre DX10/11). Ever since then, all the newer cards have been solely dependent on the DX libraries to properly thunk back to DX9--which is where the problems come from. There is so much deprecation in Micro$oft's latest platforms (not just DirectX, also .NET and such as well), that with each new release more crap gets broken. You sometimes have to go back and enable older .NET just to get a program's installer to run properly because only 4.x is installed by default.

Things like that are all because Microsoft is moving away from those older methods faster than the vendors and the users are able to adopt the new methods Microsoft is thrusting on them. Look how they had to extend the XP end of life...it is still in use in some business circles regardless of no more support for it because the tools they use won't run properly in the newer OS environments. So, we pretty much are going to have to wait for the DX11 client to see how they remedy the stability problems on new hardware and other misbehaving things like broken hardware cursor and such that have plagued the game since it went public.