Everything in that example besides boilerplate, out-of-place main() is fairly intrinsic to OOP programming in general, though, and becomes pretty much automatically understood as you learn to use it. Hello Worlds aren't meant to teach the language, they're meant to get something on-screen that the student can tweak to show ascii boobs or whatever. You don't have a print keyword ready for a one-liner hello world because it wouldn't make sense - especially not for Java, which is often run on systems that don't even have a screen. An output stream class is the sensible place to put it.
So yeah, you'd be telling them to ignore things. You're also ignoring a lot going on in the background in Python - you don't explain how Python knows what to do when you print() something to a beginner. A huge hurdle for me was learning to do that, isolate segments of code that were relevant to what I was working on, debugging, whatever, forgetting about things that couldn't have any effect on those parts, and learning to recognize what those things should look like. I don't see that as a big deal to put it in front of them right away.
I'd consider a brief explanation of having a boilerplate entry class, variables (including static vs instance if someone asks what the hell that is), and functions (including parameters - I'd segue into drawing a string from the program arguments in command-line instead of the fixed string) a good first lesson, which explains the vast majority of your example. It's enough to get students looking through the System library (hey, what happens if I use this print() function instead? Or what about System.in?) and working with the language on their own a bit. But I've only ever taught programming one-on-one with someone that -wanted- to learn, not in any kind of classroom with bored stressed-out freshmen, so that's probably a little bit too much. Maybe just ascii boobs?