Ideally it would never happen, but we know that’s not real world.
I think it would still be of use because if I started getting flagged, I would know that something is going wrong (could even be a disk failing and bad sectors cropping up, or a bad piece of software writing corrupt files). Once I know something is wrong, I could investigate and pull from (offline) backups.
One of my fears is that in tens and hundreds of thousands of pictures, something could run amok and mess things up and I wouldn’t find it until “too late” to recover (say if your backup aged out). Many people I know use commercial plans like CrashPlan or Backblaze that only have 30 day retention periods. That’s great for disk crashes and the like, but something that’s slower not so much.
At work (much larger environment) I had an instance of running across an odd, encrypted file where one wasn’t expected. It was a machine that was writing to the SAN with ransomware. I just happened to find it early and we recovered reasonably easily. If it had ran much longer it would have been a lot harder to deal with.
Some kind of warning seems worthwhile.
Obviously, this is a “down the road” thing, but wanted to plant the seed, since it seemed to me a lot of the infrastructure already exists due to other features anyhow.