TL;DR
In the context of a tutorial, it should be clear that the imperative tone is merely used to describe the action you need to perform, not a way for the speaker to express authority over you.
In essence, every tutorial is phrased in a way that assumes that the reader/viewer ("you") are intending to achieve that which the tutorial teaches (e.g. building an awesome web app), and the tutorial therefore describes the steps you will be taking in order to achieve that goal.
I think there is a distinction here that gets lost when only seen in writing.
"You're going to reticulate the splines"
This is not intended as a command. This should not read like:
You shall now reticulate the splines, I command thee
This is exaggerated for the purpose of clarity.
A more accurate reading of the intention behind the phrasing is that the person is explaining what you will need to do in order to achieve the tutorial's ultimate goal. Something along the lines of:
If you want to build an awesome web app (i.e. the goal of this tutorial), you're going to have to reticulate the splines.
In essence, every tutorial is phrased in a way that assumes that the reader/viewer ("you") are intending to achieve that which the tutorial teaches (e.g. building an awesome web app), and the tutorial therefore describes the steps you will be taking in order to achieve that goal.
Those extra modifiers are then omitted simply because they don't add anything to the explanation, and especially things like tutorials tend to boil the information down to the required steps in order to provide a short and clean explanation.
It is nigh impossible to not use an imperative tone when walking someone through several actions which you are describing in detail. In order to avoid the imperative tone, you'd have to rephrase every step, e.g.:
Click on the big red button
or
You're going to click on the big red button
into something much more verbose:
In order to build an awesome app, you will have to click on the big red button.
When explaining several commands in a row, that phrasing is going to become very repetitive and obtrusive. And even then, you're still very likely to use things like "have to" in order to point out that something is required. Avoiding even this kind of "presumptuous" phrasing (as per your interpretation) would complicate it even further:
To build an awesome app, one of the required steps is clicking on the big red button.
This is semantically so much more complex than simply "click the big red button", and the additions really don't add anything of value. They become distractions from the tutorial's main purpose: to explain how to do [X]. Anything that obstructs that goal should be avoided.
In the context of the entire tutorial, it is clear that the imperative tone is merely used to describe the action you need to perform, not a way for the speaker to express authority over you.
To get to your direct question, the phrasing you are pointing out does not make for a specific subtype of tutorial. It's a variation on an imperative, one which highlights that [the imperative] is one of the steps towards [the tutorial goal] that you wish to achieve.