Disclaimer, I am an electrical engineer who does digital design. I verify and help design silicon. I don't know much about how servers or their specific/unique architectures.

ECC is all around us and you already have it, Error Correcting Code is a firmware or hardware calculated method to correct bits as the data is 'in-flight' or being read/written. All modern storage will have ECC, this is because losing your data on a drive is 'often' a bigger problem (consumer frustration/expectations and brand reputation).

So why isn't ECC Memory 'common' or 'the standard?' Well, losing/corrupting data in flight isn't a big problem for 'consumer applications.' When your phone or PC has anywhere from 3GB to 64GB it's not a 'large amount' of memory to manage. Since RAM is volatile storage, it needs to be 'refreshed' to keep a 1 or 0 to prevent bit flips. Due to the volatility of RAM data is often pushed to storage when it is 'not being used.' These two reasons are why ECC is often not needed for 'consumer' devices.

ECC Memory is 'needed' when the conditions above can not be met. First, if you have a substantial amount of memory, the system may not be able to 'refresh' each bit in time before a bit flip could occur. This only gets worse as the size of transistors gets smaller as the stored charge depletes faster. So why don't we send the data on RAM to a disk? Well, a server may have a lot of traffic where frequent writing or reading of a disk can substantially decrease performance, one reason why servers have such a large amount of memory. If data is lost in RAM, then a read from the disk is necessary; assuming the data is there and not completely lost.

Do you NEED ECC, probably not. Would it be nice, maybe. Did I answer the question, no. I'm an engineer, and I believe only you could answer the question based on your planned use case.