> There is no world where accepting data corruption in order to save 3% cost is a reasonable tradeoff.
It is if you're doing something where corruption is detectable after the fact, and happens rarely enough that redoing affected work adds less than 3% overhead.
If you don't have ECC, you don't even know that your CPU is executing the correct code. There goes the "detectable" part.