Sort of, but I am using DCC. I have only a couple of nostalgia pieces that aren't easy to convert, the stuff I have fitting my era and railroad are all DCC already. And really, I think the only one that would be right up there with impossible to convert is an old Hornby Stephenson's Rocket. Effectively the motor IS the loco so there's not even any way to cut into the electrical path.
I gave up on Tortoise switch motors a few years ago when I discovered how cheap even commercially available servo controllers were - total package for a controller with pushbuttons, indicator LEDs, AND a DCC decoder built in, plus the servo itself, came in at less than just a Tortoise motor WITHOUT a controlling toggle or LEDs. While my ATTiny85 unit won't have a DCC decoder built in (though if I gave up the centering jumper, technically I could add the circuitry), it will drive 2 servos and cost about $5 in parts. Plus the Tinys will be good for structure lighting - multiple rooms independently lit up with some randomized turning on and off of the lights. So I'll probably be programming multiple dozens of them, which is why I built up this programmer instead of just wiring it on a breadboard like I did to test the first couple.
My signal and detection system will use Arduino Nanos plus shift registers to get extra I/O ports. It's loosely based on the Chubb CMRI at least as far as comm protocol between each controller and the computer, although I am simplifying it a bit by doing things like having a fixed message length - doesn't matter if a given controller is using 32 bits of I/O or 48 bits, they all get 64 bits worth of data, so I don't have to do as much data decoding. I'm writing the control software myself, at first just emulating a CTC machine, but my long term goal is to have a physical machine for the dispatcher to operate with the computer tucked away just doing the logic calculations.