In principle, going into read-only mode should work and it should take a while for read disturb errors to corrupt the data. But there's a trade-off that if you're trying to keep servicing writes as long as possible (and retiring bad blocks as they wear out), the risk rises that an earlier-than-expected unrecoverable error will corrupt the critical data structures that keep track of the mapping between logical and physical addresses. Playing it safe means quitting early and thus giving your drive an endurance rating that suggests it is less reliable than the competition.

And it's no surprise that the aspects of SSD firmware that by nature get the least real-world testing and are the most tricky to design would be quite buggy in practice. Even ZFS doesn't try to avoid catastrophic data loss in the face of unreliable RAM.