As for your question: coding used to be really viewed as a creative activity, akin to any other art form. Now it's just data plumbing and CRUD apps. For the people who really still view coding as an art, the demoscene can absolutely be a gateway.
I think the most important thing being in the scene taught me was how to do teamwork on a complex technical project with vague and ambiguous requirements. I didn't encounter another environment like that until maybe grad school and professional development work. It prepared me in ways I still rely on, decades later.
The competitive nature of the scene also prepares people well to work in non-academic/commercial places where the only proof of success is winning. Academia has nothing quite like this.
It was quite a shock when I first entered Assembly 93 (my first demoparty ever) in Kerava, and saw all those teenagers installing Linux or programming or making music or being awesome. Already well in our 20s, we were kind of old for the scene already. :)
I think for me, the question is how to make it a more obvious gateway. As a child we had things like the spartan C64 or logo. There are some modern equivalents but most are simple. Hard to inspire kids with that compared to what they see (vs an 80s kid). Perhaps on online repl (like shadertoy) plus a demo 101 lib with pre baked effect routines and simple graphics primitives?
Hydra is fascinating -- I sat down with it for a couple hours and was having lots of fun layering transformations on top of webcam input. https://github.com/ojack/hydra
Lua, MicroPython, TypeScript, JavaScript can play the introductory role of Basic in those days.
Followed by .NET (micro), TinyGo, C, C++, Rust, FreePascal as the next level.
Finally the hardcore kids can deep dive into Assembly.
Once your child has an intuition of how a computer works its pretty trivial to teach programming. There are still lots of language specific gotchas though.
Many schools in the US have organized robotics programs, but those are expensive and require a lot of support. Making a demo is know how, and some HW.
Probably the main thing missing is the the materials. I've been skimming through the links here to find good starting points. Its a lot to collect -- many of the entry level techniques are so old, they're not always written up (or the target audience is different).
Never did get around to making my own demo, but I owe finding my career path early in life to the demoscene. So many fond memories (esp early 90s through 00s).
I have and will spend countless hours coding to demoscene music (good and bad). To me, the unique thing somewhat lost in my avg day to day development life is that this is a fundamentally self driven challenge that can cross many CS disciplines combined with the art of practice. A demo pushes one in many directions at once: art, math, graphics, data structures, optimization, mechanical sympathy, sound, etc. (There's a reason there is a lot of game dev <-> scene crossover.). You can work in isolation, or as a group. However, a group is more common since most people can't do it all.
Digression aside -- Could we use the demoscene as a gateway for future engineers? A STEM + demo style toolkit?