I don't think that would've helped — I'm pretty sure the dev tools folks work in another building.
I read through both forums threads you linked to, and neither contained any information about how to reproduce this issue in a self-contained project. "+1"-type posts are not helpful — and sadly, for extremely circumstance-dependent issues like this one, neither is "here are general details about my setup" because it's simply not enough information to go on.
I can't speak to the feedback you filed, nor do I work at Apple — but if it's not actionable then all it can do is be a "+1" to a pile of "we know there's an issue here but we haven't been able to reproduce it in order to fix it". There isn't really much that can be said in that case.
Because good feedback is immensely helpful internally even if you don't hear about it publicly. Apple never comments on anything unreleased, nor do they discuss anything under investigation. When I did work at Apple, I really appreciated getting reproducible feedback that led to actionable bug fixes, even if the reporter couldn't receive public acknowledgement for weeks or months. That was as frustrating for me as it was for the reporter, but at least the bugs got fixed.
If Apple didn't care, they wouldn't prompt for your feedback at all, or offer a way to provide it, or respond to threads like this asking for additional information to help reproduce and fix the bugs you're seeing.
I don't feel attacked, but comments like these make for an unwelcoming environment, both for folks who read these threads, and for, y'know, the people actively trying to fix these issues.