Take a look at Restic for backups. Rclone and Restic play together really nicely.
Fortunately there is https://github.com/creativeprojects/resticprofile to solve that problem.
I hate such an approach when someone assumes that whatever happens their opinion is the best one in the world and everyone else is wrong.
I do not want to encrypt my backups because I know what I am doing and I have very, very good reasons for that.
Restic could allow a --do-not-encrypt switch and backup by default.
The arrogance of the devs is astonishing and this si why I will not use Restic and i regret it very much because this is a very good backup solution.
Try Borg.
I'm using duplicity because none of these can sync to a rsync server that I run on my NAS.
As for remote backups - I use ssh with Borg and it works fine. If this is a NAS you can probably enable ssh (if it is not enabled already).
BTW for my remote backups I do encrypt them but this is a choice the author of Borg left open.
There are other issues with Borg such the use of local timestamps (naive date format, no timezone) instead of a full ISO8601 string, and the lack of capacity to ask whether a backup is completed (which is a nightmare for monitoring) because the registry is locked during a backup and you cannot query it.
Restic for various machines to hourly backup on a local server. Rclone to sync those backups to S3 daily.
Keeps the read/write ops lower, restores faster, and limits to a single machine with S3 access.
Duplicacy is slower and also only free for personal use.
The rclone backend means I can backup anywhere.