and rclone sets all created times to now() instead of keeping the original value.
Windows (didn't try linux) shell copy will preserve these times when copying files from one drive to another so this should be possible for rclone as well. If not desired it hasn't to be the default but at least an option via a --keep-created switch would be nice...
i agree that robocopy does not have versioning and that is a critical feature.
i never use robocopy for backups. i use robocopy for moving\copying around files on an adhoc, as needed basis. robocopy can do something few tools can do, copy EFS files in RAW mode from server to server and NOT have to decrypt the files during the copy/move, which is critical if you have to deal with HIPAA regulations and audits.
also, robocopy will not use checksums at all. neither to determine what needs to be copied or to verify what has been copied has been copied without error so it cannot be trusted for backups.
and for speed, you cannot beat fastcopy which can use checksums
for versioning, i have a couple of solutions.
for backup of critical infrastructure such as servers, i use veeam backup and replication, which has versioning and a whole lot more and use rclone to copy that to the cloud.
for certain data folders, i have a script that will compress a folder into a .7z with the date and time embedded in the filename and use rclone to copy that to cloud.