Thank you for the idea. There are a number of reasons I prefer to stay with the RP2040.
First, I have been reading deep into the RP2040 support for state machines,and I think it is ideal for what I am trying to do, as far as interacting with bus controls, memory cycles, etc...with pretty much guarantied timings up to a level. I think I could even implement instruction step by step.
Second, I can program most of it if not all in micro-python, even the state machines. I do not believe that would be an option with ATmega. If I was to take another MCU, it would be in the STM32 line, supports micro-python and I have done some work with hem , but I looked into it and discarded it.
Third, I have never touched the ATmega line, and the appeal it may bring is not enough for me to move in that direction now. May I add I am way up there in age and this may be the last project. In fact I have been unloading some of my lab equipment, HP and Tektronics scopes, meters... Witch now, I may need to buy a low end scope for the project, but it is not about money.
Fourth, I want to a GUI from PC, and with micro-python, I can have an HTTP server. At a later time I can switch to the newer RP2040, with WIFI/BLE.
I have been thinking about it for a few weeks, and I think this weekend, I have solved the last hurdle, the GPIOs layer.
Thank you for your idea though.