Our code base creates around half a gig of compilation product on every build. We used up the endurance on a consumer-level Micron SSD in about a year. No data loss occurred.
Just food for thought; your point remains valid.
But the point about SSD endurance still stands, a ramdisk solves that problem.
Is there ever a reason to commit to disk anything you don't keep after a reboot?
500MB? That's tiny in comparison to available RAM today, so I would just say use a RAMdrive and periodically write to the SSD.
Bandaid solutions (replace every x months, buy something bigger/faster, etc) are not the way to go. The hardware solution to this is not buy a high-endurance drive but to buy more RAM and set up a tmpfs build directory - or buy a ram drive and use that for build instead of you want to eliminate even that software configuration step.
It may be far cheaper to do so than to spend developer time coming up with a ramdisk solution. And RAM is far more expensive, per GB, than SSDs.
Next year's drives will be cheaper and better, anyway.