I use Btrfs with Parabola GNU/Linux-libre, a derivative distribution of Arch Linux. I use no snapshot management tools such as Snapper or Timeshift. I keep my system minimal and tidy. Everything is boring and predictable. I do not bork my system by mistake, except when something breaks after an odd update, usually once or twice per year. When it happens, I find a workaround (usually something needs to be downgraded) and file a bug report if there is none.
When I need to tinker with something that can possibly go out of control, like installing a new package for a program that I want to try out and I am not sure I will want to keep it, I take a snapshot of my current “pristine” system and boot into it. In the snapshot copy of my system I do all the dirty stuff I want to try out. When I am satisfied with my findings, I reboot into the main subvolume and delete the snapshot.
It seems to me that most people use Btrfs snapshots preemptively in case of unexpected failure. I use snapshots exactly when I know I am going to do something that can lead to instability or «OS rot». Am I the only one using Btrfs snapshots like this?
You can do (most) of this without rebooting by leveraging the btrfs support built into systemd-nspawn, which allows creating ephemeral data volumes to mess around in. It’s meant for containers, not the semi-Silverblue system you’ve set up, but it may save you time messing about with new tooling.
It should also be noted that although tools often miss support for it, almost any LVM2 filesystem can do snapshots if set up with enough free disk space for them.
I just use a package manager hook to set up btrfs timeshift snapshots whenever I do something to the root partition, but to each their own.
systemd-nspawn is interesting. I never managed to try it out.