I think developing on a laptop and hoping it will work on an ETC could lead to disappointment.
I dont have an ETC, but ported ETC to the Organelle which has the same hardware, and i think one hurdle is pygame on it doesn’t appear to have any hardware acceleration (odd as the underlying integrated GPU does), and its cpu is not that powerful compared to a laptop.
also there are some assumption made in the ‘mode loader’ (the software that invokes your pygame modes), about how the screen is refreshed and ‘blitted’ to the hardware, that might not be optimal for sprites, however, if your ‘handy’ with python (and have a wifi adapter for the ETC) , its not that hard to change the mode loader to do whatever you want - i found it pretty simple to understand/adapt.
for me (others may consider this untrue) - i think the ETC (and Organelle, rPI etc) are a fun challenge to develop for, its more like the old days where the ‘game’ was , how much can i get out of this?
rather than todays development which can be, I’ll just throw more $$$/CPU/Memory at it, and do a sloppy implementation
So Id say, if you want an ETC (due to its hardware interface e.g. MIDI/sound input/buttons/knobs) , then go for it… you obviously know Pygame/Python, so you’ll be at home… and once you get it, approach it more from a what can I do given the constraints, and also its unique properties.