To answer the original question: no, there isn’t a comprehensive list of accidents caused by OSM (other than the mapper-volunteered list you found). Depending on the situation, it can be very difficult to attribute an incident to a navigation application. While a list of such incidents might inform our mapping practices, helping us develop more robust tooling and procedures, we’d need to tamp down any unhelpful speculation and avoid “shooting ourselves in the foot” with legal liability.
We can learn lessons from accidents whether or not OSM is at fault. I can’t definitively prove that Amazon retagged a golf cart tunnel because one of their delivery vans got stuck in it because one of our golf mappers used an unfortunate preset, but we fixed the preset and mitigated the issue regardless. Hopefully this lawsuit blaming Google Maps for a fatality underscored for us the importance of taking notes seriously instead of hastily closing them to score cheap points on a leaderboard. Alas, this thread has repeated many of the same discussion points as that thread, so maybe not.
No one ever implicated OSM in this fatal crash involving a freight train, but the authorities nevertheless demanded that OSM and our data consumers take positive steps to warn motorists about railroad crossings, because they recognize the potential safety benefit from location technology. OSMUS was able to inform regulators about the steps that this community had already taken, on our own volition, because we care about the craft of mapmaking. It’s one example of us leading the map industry rather than playing catchup. On the other hand, if we had lectured the regulators and legislators about user responsibility or dragged our heels like some other map vendors have, I don’t think our case would’ve had such a favorable outcome.