In any case, "write-once" media can still be rewritten; the same lasers that etch data into a CD-R can do so to destroy the same data. You're going to want redundancy/backups and you're going to want each new row in the table to cryptographically reference the previous (such that any data destruction invalidates all subsequent rows) - by which point you've reinvented most of what constitutes a blockchain anyway.
I do believe Write-Once was actually a thing with the banking mainframe I was acquainted with in my youth. It wasn't a CD-R thing, it was just an IBM thing which enforced write-only at the BIOS/Hardware level. Honestly, I'm not sure, I was young and impressionable :D. IOW, I might have been misled.
Anyway... All you need is logically write-once with proper signing, audits, etc. and you'll be just as close to unforgeable, etc. etc. as reality demands.
Heck, even journald on Linux provides unforgeable log entries. It is vulnerable to a destruction attack, so whatevs. Everything is. Even a blockchain -- witness the rugpulls.
> by which point you've reinvented most of what constitutes a blockchain anyway.
I love that.
Anyway, I'm here to dissuade you. Do whatever you want. Just be aware of the potential consequences.
By the time you build a system with historical "proofs" with enough replication, you'll basically have invented a Blockchain with more complexity.