Realistically, reaching out to developers individually does usually get better traction. That involves going around the project's due process of posting to a list. That raises the bar to getting to the bottom of the problem even further.
I guess that discussing the likely impacted area is possibly the next increment in analysis, but even then you will still have the people turning around and saying "you have no idea what you are talking about, stop spreading FUD".
Not an easy problem to fix, but *very* costly to make valuable.