Does a Big Sur 11.x Update kill genuine Apple SSDs in MacBook Pro 13" Early 2015?
No. We have that update on several Macs identical to yours. You may have a hardware failure, but it’s not the OS that’s causing it. The OS is hobbled by it no other than needing the next write to succeed, there’s no code in the OS that intentionally breaks storage.
As it has been for two decades of Mac OS support, coincidence is more likely than cause, here. It stinks when we get a failure, so no amount of experience lessens that disappointment. Worse, it shakes our confidence when we confront how little we can do in the face of hardware failure.

When you run an upgrade, you change the boot process substantially. This is precisely when you discover hardware isn’t up to snuff and pre-existing storage failures become critical. (This is also the time when minor  storage corruptions turn into data loss.)

Separating causality from correlation is super tricky outside a repair shop where you have access to known good parts, can reconnect cables, run advanced diagnostics and see trends due to hundreds of repairs a week.
Your next step is to contact Apple for a service estimate. They may just offer a service program and underwrite the cost of the repair. Worst case, you have a second look at your triage and know one cost for repair.
In the mean time, you can try erasing it from several OS, but be sure you keep good backups if you “revive” this Mac.
p.s. this sort of error is precisely how many of our SSD bite the dust. We gladly pay for repairs on 2015 and newer gear as they run great with new SSD or logic boards, even on Big Sur.