One way to see this - assuming you are confident of the problem - what is a practical course of action? Have you found the line(s) of code that are the definite cause? If you can't fix it, you have to:
- Fix it yourself
- Convince someone else to fix it.
So, how are you going to accomplish #2? If all the evidence you have is mysteriously buried deeply inside a proprietary program that also uses an RTOS, but you can't actually point to the cause, you are asking someone else (who is not hearing any complaints from anyone else) to dig through all that stuff for you. How many hours do you think that would take? Any renumeration? I didn't think so. So put yourself in their shoes. That is what an MRE does, takes the burden off the maintainer by isolating the problem.
And - this is an Arduino programming forum. Not an AVR-GCC code hub. You can complain here all week and all you would get is sympathy or the lack of it. To get action on something like this, you have to open a pull request or whatever the maintainers use to track bugs.
Also, compiler maintainers don't care about applications. They only try to guarantee that the language specification is adhered to.