OK, well that was easy. I fired up VMWare Fusion on my Intel Mac running MacOS 10.14 (Mojave). I've got Apple's Snow Leopard OS running on Fusion.
Then I just copied ScreenLogic Connect from the Application folder of Mojave to Snow Leopard. ScreenLogic fired right up, but couldn't find my EasyTouch. Turns out I had never configured the Network Adapter of Fusion properly. So that took a few more minutes and then I re-fired ScreenLogic and bingo! ScreenLogic works fine, including the Configurator. I made a small change using Configurator. And I started up an Aux circuit in ScreenLogic. Then I quit that ScreenLogic and started the Mojave ScreenLogic and both the configuration change and the running Aux circuit showed up as expected. I didn't test more thoroughly than that, but so far I think I have a solution for upgrading that Mac to Monterey without losing ScreenLogic. I'll report back when I upgrade that computer. It's possible that ScreenLogic won't run in Fusion when Fusion is running on Monterey instead of Mojave, so we'll see. But I expect it'll be fine.
And I actually did all that "work" from my M1 Mac! I use the MacOS's built-in Screen Sharing feature to operate any of my computers from any of my other computers, even my iOS devices. I can "see" ScreenLogic running on Snow Leopard running on Fusion running on Mojave running on a different computer from my M1 laptop! So, technically, I have ScreenLogic available on my M1 Mac, and will even when it will no longer run natively on that Intel Mac (when I upgrade it to a 64-bit OS). That's not a solution for everybody running a Mac, obviously, but at least it's a possibility for some.
Ha, technically, that was the Windows version of ScreenLogic running on Wine running on Snow Leopard running on Fusion running on Mojave running on an Intel Mac computer operated from an Apple M1 laptop! Hey, what could go wrong?!
But much more importantly, I don't have to get out of bed to run my pool!