Same here. I recall having an issue with Yosemite that was difficult to reproduce, and the apple engineers and I had a fun (I mean actually fun) deep dive into recreating the issue. It turns out it was a unique processor specific issue that was ultimately harmless for the vast, vast, majority of the population but had significant effects for my work (literally a specific CPU instruction change that would normally be harmless or beneficial for everyone screwed up my work).
Basically I was Longtimeuser4:
View attachment 2600399
I say
was because I submitted a few similar issues with the m-series and Apple closed them without a resolution until the gofetch vulnerability was discovered (my issue was somewhat related to how the M1 cache operates), and they suddenly reached out.
Anecdotes aren't data, but on a personal level the experience of having a submitted issue 'resolved' without doing anything until media attention forced action has ensured that I'm not going to waste more time documenting and investigating any future complex errors.