The issue about replying might be a monetary one...
"if" your bug report or feedback brings to attention something major (let's say) and Apple responds and/or gives you some type of credit for it, users sometimes expects or demand compensation for their find or their "assistance".
Also, YouTubers and others can profit off of having proof by a response email that their bug report caused Apple to change or fix something. There are many reasons why they don't respond, but my guess is because someone would figure out how to get money from Apple or gain from it legally if they respond. Apple is above their heads in legal stuff, so they don't want to add to it.
Back in 2012-ish, an update to Logic Pro broke A LOT of DAWs functionalities across the board (many brands). I actually called into Apple support at the time because I was working on a project and everything halted because of the update. The rule of course is to never update during a project...but I needed too as the update should have fixed an error (as stated in the support notes) I was currently having.
Well...the tech support actually told me to hold and they transferred me to a very thick accent older German man engineer at Apple and after some time, and I realized after a lengthy discussion that it was probably the actual or one of the original Logic creators still at Apple at the time.
Apparently, he said that Apple Execs were giving him a bunch of heat because the Logic update they put out broke some major things and they wanted it fixed right away. This was around the time when Steve Jobs was still around (just before He died) and it was right around the time when FCP came out (a year before I think) and pros were exiting fast from FCP due to the "New" changes, so Apple probably didn't want Logic "Pros" to run either.
I was a semi-pro type at the time, but the engineer asked me a lot of questions and I was able to answer most of them. He said, "The big wigs want me to fix it, but no one is telling me what the issue(s) are..all I hear is FIX IT." So, He actually listened to what I was saying at the time and later thanked me for taking the time to talk to him and to help him out and get the heat off of him from the Execs. I was irritated with the issue at the time, but I enjoyed talking to him so much, I left the conversation more understanding...and was impressed with the ownership he had over his work and the issue.
It showed me that when you give feedback or send in a report, give them actual intelligent and technical language explanations so they can understand what is wrong instead of just saying, "My printer doesn't work" (those who are old tech support people should understand what I mean by that... 🤣 That is also maybe the reason why they don't respond anymore.
Because people call up or send in complaints, attitude and just vent about their frustration (understandable) about why something broke or cause them issues. My talk with the Apple engineer (probably the creator or high up) showed me that "YES" they listen, but they are more interested in getting understandable information so they can fix it, not just complain. Not all who submit complain etc. of course; and many who submit reports to Apple on these forums are techies and probably send in good explanations, but I would suspect in this time and age, many send in more so complaints and competitor companies or Apple haters send in (paid) false and fake stuff just to cause delays or complications etc. Just like trolls on these forums. Nothing is new.
Anyway...Since the guy seemed "old school" in his way when I was talking to him, I decided to asked him if he could also help me out too (scratch my back - I scratch yours - old school payback) and asked him if he somehow could extend my current DAW for a little longer in usage (because old DAWs were dropping Logic support at the time to make room for the newer - plus, my DAW was firewire and at the time, firewire was dropped also).
I then told my story of actually talked to the third party engineers who created the drivers and they told me that "if" the main company would call them and request (pay) for the updates to the drivers, they would do it...but they did not and never did. So I was out-of-luck, but wanted to continue using my Alesis MasterControl for a little longer before itbecoming a door stop. (side note): Alesis was being sold to an investment group at the time and was probably the reason for no interest updating old drivers now. I did not know at the time. So...many reasons why some things don't get fixed.
All that said is to show there are MANY reasons WHY things behind the scenes are not known and we all question: "Why doesn't Apple do this or that...?" There are MANY reasons why things don't get fixed or not addressed. Not giving excuses for Apple (I am one who is irritated with macOS Tahoe and waiting for the next update in hopes that it resolves some of my issues), but from experience directly, there are more complicated issues going on then just "fix" this or that.
Easy it may seem to "just fix this or that", but there are reasons why, and we just have to live with unfortunately.
or..go to Windows or Linux which is not on my option list.
