I think if the idea is to help newcomers with Vim, this is the wrong approach. Nobody tries to learn something new by checking out what a random key does, using :help X. When I was trying to learn Vim, the most useful info was actually search results for "how to do X with Vim", because everybody knows A) another editor, probably B) what they want to achieve. After that you slowly discover features one after the other, which can only happen by using the editor a lot. It's good to have a "help X" around, but most of the time, if you're starting out, you don't know that X is what you need in the first place.
People learning git don't start with typing "git rebase --help" just to see what it does. You learn to add, commit, push, (probably from a tutorial) and then go from there.
Hence vimtutor. The "going from there", in git, does consist in part of "git rebase --help" or "man git-rebase", which are roughly equivalent to :help.
Not to start with no. But as I started to become familiar with Vim enough, I realized I reached for :h more than go search google, and for the most part, I found what I was looking for in Vim's help pretty easily and much faster than google. Vim's help is easy enough to use that you can `:helpgrep topic` or just `:help top<tab>` to list all the help topics and go from there.
Sure you can achieve the same thing by searching online. However, I believe that reading Vim's help motivates you to learn more commands and be more efficient with it. There's so many things in `:h motion.txt` that online articles don't mention and I would probably never come across them.
Similarly, with Git, I did learn to add, commit push but then I learned to reach for `git help topicname` if I want some documentation on that topic name.
People learning git don't start with typing "git rebase --help" just to see what it does. You learn to add, commit, push, (probably from a tutorial) and then go from there.