> If not, why not?

At least on Apple devices, this is not something anyone has to worry about.

For example, on my 2022 Mac Studio daily driver, on 24/7, DriveDx (https://binaryfruit.com/drivedx) reports my SSD lifetime left at 94%.

(I'm aware of the February 2021 "wear-gate" scare involving the first M1 Macs. This turned to be incorrect SSD-wear reporting.)

Just configure wear leveling in your storage layer. FDE may be the easiest way ti do it. Writes will be done linearly in circular fashion. That makes it difficult to delete stuff, but with encryption it's moot.

why do you think this is a function of betas? or even of OS or app versions?

I guess you've been burned, or are worried about being burned, by some software that generated excessive writes? I think you need to describe that first, since this is a rare phenomenon.

which is probably why there isn't some kind of downdetector infra tracking it.

you know you can access smart counters on any OS, right?

If you are not using bottom of a barrel and you are not writing 4K HD 3H mkv every day then you wouldn't have a problem even with a 0.3 DPWD drive of a sufficient capacity.

I feel like the only responsible thing is to have a home network with at least one persistent device running 24/7 with large storage for local backups of things, and ideally a E2E cloud backup of the same thing. With this, comes the possibility of using things like Grafana+Prometheus to monitor your personal computer/workstation as well. This is what I've done, together with alerts from various things, and since the recent "excessive writes by codex" issue, also alerts if there is obsessive writing over hours long period from any process on my workstation. Luckily I wasn't hit by the Codex issue myself, but certainly made me consider the issue more generally so, happy accidents :)