You could also consider a bind mount. Whether you do it VIA systemd or fstab, you can automount it. I have quite a few of those:
$lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 3.6T 0 disk
└─sda1 8:1 0 3.6T 0 part /mnt/4tb_backup
sdb 8:16 0 4.5T 0 disk
└─sdb1 8:17 0 4.5T 0 part /home/mirdarthos/virtualbox
/home/mirdarthos/Video
/home/mirdarthos/Pictures
/home/mirdarthos/Music
/home/mirdarthos/KeePass
/home/mirdarthos/Documents
/mnt/5TB
nvme0n1 259:0 0 232.9G 0 disk
├─nvme0n1p1 259:1 0 500M 0 part /boot/efi
├─nvme0n1p2 259:2 0 7.8G 0 part [SWAP]
└─nvme0n1p3 259:3 0 224.6G 0 part /
See
and
Edit:
a Symlink is just a “shortcut” to a file or directory. You link a destination to a source. I don’t know where the “sym” part comes in.
Edit #2:
Indeed, see here:
If you use Windows, you’ll recognize the function of a symbolic link in the structure called a “shortcut” – a text string that your OS automatically interprets and follows, pointing to another file or directory; this allows one file or directory to refer to another, on the same disk or different disks.
This is different from simply making a copy of the target file or directory because it doesn’t take up hardly any space, and instead of then having two different copies of the file, opening the symlink opens the target instead, and any changes are propagated to that target.