First, I'll say that I don't think that devs, and more specifically game devs, shouldn't learn C, I just think people shouldn't learn C first these days.
I think it's absurd that your first program (Hello, World) should involve a static class, a static method, and object method calls.
But, you have no problem with includes, function calls, etc? Isn't that overly selective?
I'm sorry, but that's a silly way to argue for a low-level language over C#/Python. The typical "Hello World" example is usually a couple of lines in any language. However, it doesn't serve to illustrate the overall TCO, if you will, of learning a whole language, its available concepts and techniques.
Simplest workable "Hello, World" in Python:
print "Hello World!";
public class Hello
public static void Main()
Looks like Python wins in terms of simplicity!
In any language, much like in C, you'd slowly introduce structures, functions/methods and more complex ideas like algorithms and best-practices on structuring code. In the long-run, there's some stuff in higher languages you don't worry about that you still have to teach in C. Thus, you get more productive faster with C# or Python.
These were mostly due to the fact that some of these guys really never really got much experience dealing with memory management. A lot of them had started in Java only had a cursory understanding of C or C++
OTOH, you hire the C student who can't conceptualize the larger picture because they spent too much time learning how to get their pointer pointing on point and their buffers to not overrun. Lots of them learn how to "architect" code after they have left school and give you spagetti code to deal with, like a cat leaving you a dead bird as a pleased gift.
So, while I understand (and totally empathize with) your frustrations, that still doesn't point(er?) to learning C first. What you have in your scenario is a dev trained in a high-level language suddenly being put in front of a language that doesn't do certain things automatically that they are expecting, thus they do it themselves wrong the first time around. The problem is not that they don't know C, but that your hirng process was f'ed up.