I use Tumbleweed as my Desktop, as well as on a server or two. I agree that it is rock solid. The only loose canon is NVIDIA.
On the other hand, we have measurement systems that are not office bound (road condition measurements, mobile mapping, etc). They need to be stable as we can make them. And, it is not convenient to update them regularly as they are in the hands of customers. So we usually choose a Leap release and then use that as our official release for a couple years. We make an installer using KIWI so that every system is 100% identical (baring any hardware differences that we cannot control). Every couple of years we move to a new Leap. It is a workable solution; however, it gets more difficult after our Leap is EOL and we need a new package that was not in our original KIWI install. As long as the package exists, we have a method to get them into our systems in a controlled fashion. But after EOL it gets to be a crap shoot. And an indicator that it's time to make a new KIWI installer and re-install the systems. Rinse and repeat, as it were.
We had toyed with using Tumbleweed in this context. Unfortunately, the rolling release that I like so much on my desktop is a problem in this other use context. Getting all measurement systems to have the same Tumbleweed snapshot at the same time is like herding cats. As we deliver a binary installer, matching library versions across independent Tumbleweed versions is near impossible. Also, our current approach does not require an Internet connection at any point in the system build/maintain process.
Does slowroll address our situation? I'm not sure. If something like a Tumbleweed's zypper dup could be done with slowroll but at a far less often frequency, and if a slowroll release could be around for a bit of time thus allowing different systems to get to the same slowroll release but done perhaps weeks apart, then perhaps it might.
If anything, this discussion has us looking at the possibility of making our software into a flatpack. It has dozens of commands so the task is perhaps involved. But decoupling our code from the underlying OS might be a good thing. We already do something similar to be able to build Leap 15.3 (our current Leap) programs in our constantly changing Tumbleweed build environment. More of a chroot setup. But still a separation of our needs from those of the OS.