3-2-1 is ideal, but Time Machine is really best as an on-premises backup, with some other backup utility for off-site network backups, unless you are going to unfailingly move disks to an off-site location.
Consumer rotating rust drives can be good when run solo, but when in an enclosure with other drives, the combined vibrations take their toll on the drives. NAS rate drives are more tolerant of adjacent drives vibrating the enclosure.
Using a direct attached JBOD concatenated drives to make a bigger volume is fine, as that system is most likely dedicated to backup, and if it fails, you just start over again, because it is a backup and not your original work.
However, if you get a NAS, you are tempted to use its other features, such as a personal dropbox equivalent, a video server, your own home VPN, a personal web site, etc... In that case using RAID so a single disk failure does not take out all the OTHER stuff you have on the NAS. And yes, the files you are using that are not related to a backup, need their own backup. I have a 2nd NAS in a diagonally different part of my home which just backups up the primary NAS. It is NOT "Off-Site", but I'm hoping that one or the other NAS will survive a disaster.
Agreed that RAID is not a backup, but it is useful in that when a drive fails, you do not need to panic that you are no longer backing up. You can take a little time to get a replacement drive, pull the failed drive, plug in the replacement and allow the RAID box to re-silver everything.
One of the nice things about Synology is you can have "Hot Spares" so that if a drive fails, a drive is sitting there waiting to be put into service for the failed drive. Synology also has RAID configurations with 2 redundant drives so loosing 1 drive means you still have redundancy, until you loose a 2nd drive and then you are still functional, but cannot afford to loose any more drives.
From an admin perspective, RAID gives you some flexibility on when you need to replace failed drives.