well, in your case, you have a inside view of rclone and can choose a stable beta version.
in my case, never use beta software.
in fact, i try to stay on step behind, still using v1.55.1
for the rest of us, that trick will require always using an unstable beta.
new bugs on existing features can sneak in, such as the current issue with --daemon
i believe this problem will not go away, too many hacker tools are using rclone and that will increase.
microsoft and other anti-virus providers have zero incentive to whitelist rclone.exe
for most rcloners, simply whitelisting will be a good enough solution.
for others, who use rclone on many machines for critical backups, having a bunch of those backups fail at any time, and all at the same time, is a nightmare that needs better solutions.
having a .exe disappear really messes with workflows...
so far, my workarounds are still working.