2 - visual builders probably exist now and will certainly exist later. Programming is getting more and more high-level, more accessible.
glade, visual studio, unity, etc. Yeah, visual building has been around for a long time now, and the coding is minimal when it comes to gui. They usually have a way to add code via a typing interface, to help glue things or add functionality, but it's already here. I've seen examples of visually built programs on GOG: all the gogrepo gui frontends. Behind the scenes, i imagine, it's all plug'n'play level stuff that doesn't even go as far as using equality operators to fill in the stuff. Actually, i think some of this stuff is older than GOG itself, so it's worth being aware of.
I've noticed, though, that it actually makes programming less accessible. It's more akin to driving. These visual bits are like the Barbie trucks. Then next up you have the scripting languages like JS, python, etc, which are a bit like driving a go-kart: doesn't go very fast for complex operations. Then you have the languages like C, C++, Java (yes, it's now got native binary support on Android and iOS), etc, which is like driving an automatic. Assemblies are like driving a stick shift: you'll get more control over your vehicle, you need to understand it better to keep from screwing up, but that extra requirement also makes you better at handling an automatic, and your manual overrides to the gear system can give you more power or milage depending on your desires, but the differences will be limited, but it also gives you access to 18-wheelers (sub-kernel). And, yes, I've played in these 4 levels.
3 - I don't think most would play if it got bogged down in learning a language. Especially if you're interested in python and the game teaches Visual Basic.
Yes and no. I learned C++ because I wanted to make missions for Star Trek: Starfleet Command III. I ended up not understanding enough of the build process to actually succeed, unfortunately, and had trouble getting any kind of help. Now that I have done assembly and have worked with the build process a bit, I understand now that I had done things that weren't unnecessary that i thought were that made it way, way harder to develop the mods, which is why I had never succeeded.
I think the big picture here is the chicken and egg issue, which is something I've learned when trying to help people with their programming studies and trying to help people learn coding outside of a classroom. At the end of the day, people see a long and hard journey ahead of them, and they want something to chew on and be proud of very early on. This is why languages like perl and python get gobbled up pretty quickly 'cause it avoids boilerplate code. On the flip side, they also don't want that long, painful journey of hardship and brain bending to be learning something that doesn't have the full tools available to them (so, like, if someone ever dreams of coding a game, getting them to learn PHP first is not going to fly). Of course, you and I both know that once you learn C or C++ or something like that, learning Visual Basic, Java, Python, etc is really easy, since the fundamental concepts behind the challenging parts to understand are all pretty much the same. However, we cannot communicate that to people. I think this is what timppu's problem is, because he's not demonstrating something here, that says "i'm a coder," but rather that he's certainly interested (i could be wrong though) demonstrated by awareness of certain topics, which implies to me that he's afraid of investing and getting burned. At the same time, people like him are very afraid of a raw, unguided investment, which is also what makes him the target audience of something like this: regardless of whether or not it actually works, coding game advertisements prey on your fear by promising to make it easy for you as opposed to raw learning.
I would invite timppu, or anyone else, to go ahead and spend a whole day off learning C (should be perfectly possible to get through all examples and at least half-understand the ideas in one day). You'll not be perfect at it at the end of the day, but a decent C tutorial that covers all topics is enough to get your feet wet, and going through the whole thing again 2 or 3 times after you realize how short and manageable it actually is, you'll probably take a week or two after work or school to learn the rest by going over it again with a fine toothed comb. If you find C hard, contact me and i'll set you up with some kind of assembler: assembly's supposedly harder, but it only is harder through it's simplicity: it's easy to understand but harder to put to practice, and I can help you get started in x86 or on android (the timer for android is running out due to some policy changes) without a series of complex tools (and I believe i can teach you assembly in about 2 hours by comparison, and you'll quickly take that up to learn C in about 4 hours making the process even faster than going straight to C, however i don't offer it first 'cause it's harder to find material to help you go that route).
I wish i had myself as a programming teacher: I would've accomplished my goal.