We already got their initial response to the concerns here:
It’s unlikely we’ll hear more than a “we’re still working on it” before they have at least some solution ready to deploy. When that will be is anyone’s guess, since we’re not just dealing with a stacking proc exploit, but physical and visual accessibility issues as well. As much as I hate dealing with the theme from a visual perspective, I’d rather they put priority into getting rid of that exploit. Then they can devote their resources entirely toward figuring out the best compromise for the physical and visual accessibility issues.
However, I’m just as much for them taking their time and watching all of the exploiters carefully so they can smack them in the face with an Error 52. That works for me too.