(Resending after a permissions snafu)
I already went through our outstanding CABF issues today, as the next major effort now that SC41 has been merged  is working on a "Cleanups and Clarifications" ballot for things not related to certificate profiles, while continuing work on certificate profiles  for those related to extensions/field contents.
This issue hasn't been dropped or forgotten; rather, the focus has been on trying to improve the agility of the CA/BF through tooling and clearer requirements, so that we can continue to address issues like this. If you're interested in helping, joining as an Interested Party is a great way to help contribute!
In the interim, it's totally something that Root Programs could choose to address via their policy. Although Mozilla just published their latest version of policy , you could always see if Mozilla would like to address it in a future update of their policy via .
Hope this helps!