People keep manually mounting network shares, causing hangs, and then blaming KDE code for it

We have KIO which provides asynchronous file access. We have kio-fuse that extends it to apps that don't use KIO. But none of that matters for network mounts that have been manually mounted using /etc/fstab. People keep doing that and then complaining in bug reports and reddit posts that Plasma or some app hangs. Most recent example. I see this at least once a month; it's clearly a pain point for users even if we solved it years ago. But they don't know!

...Maybe we should tell them. I'm imagining we could have a small program that parses /etc/fstab at boot (or even upon receiving a notification of changes to that file) that opens and and detects the presence of manually-added network shares. Then it could display a dialog to the user saying something along the lines of, "hey, did you know this isn't needed and can even be harmful? I can replace the mount with a shortcut pointing to the network location and that will work much better. Would you like me to do this now?" With buttons saying, "Do it" and "No, ignore this mount". Then if the user clicks "No, ignore this mount" we go on to explain that it can cause hangs in GUI apps and they're on their own if they do it, so please don't file bug reports about it.

The idea might seem silly, but without something like this, I fear we're going to be fielding complaints about this forever.