You can snapshot them independently. E.g. I snapshot / on every update and boot, /home every boot, and temporary file directories such as /tmp & /var/tmp don't get snapshot at all and are also mounted with nodev,nosuid,noexec flags.

You snapshot them separately, with snapshots stopping where another subvolume starts. Have a problem booting? Copy the latest /-snapshot. But if for example /var/log is a separate subvolume it persists and you can look up what was wrong.

My setup right now has subvolumes root(mounted to /), home(mounted to /home) , logs(mounted to /var/log), snapshots(mounted to /.snapshots), pacman-cache(mounted to /var/cache/pacman) and swap(for the swapfile obviously).

I do snapshots of root, home and logs (landing in snapshots) regularly that don't require much space (only the difference between on subvolume and its snapshot uses real space in btrfs) and which can all be restored together as well as separately, while losing the temporary data in cache and swap is not problem.

And you can also transfer the snapshots somewhere else as backup (into another brtfs filesystem or as a file), including just transfering the difference from the last one as an incremental backup.

For one thing if you're snapshotting your subvolumes for backup purposes then it will ignore nested subvolumes. Eg you dont want to preserve snapshots of huge installed game directories, cache directories, logs or docker / podman images, usually. Saves a lot of space.

Also you can tune copy on write on a subvolume, which is great for some use cases for performance.