Well, it kind of forces readers to follow. I mean, if you stop after part 3, you have a RedNAND and no CIA manager. If you do part 4, you dumped OTP so it would be stupid not to install a9lh. So there is no breakpoint where you have both a CFW on RedNAND and a CIA manager without a9lh. So yes, you could stop in the middle of it but you have to guess where. Because "Part 4, Section I, step 17" (RedNAND and CIA manager) looks as much like a breakpoint as "Part 4, Section III, Step 3" (in the middle of 2.1, without even an SD card in the console).
And then, you also have the fact that it gives steps to get to a certain place but not other places. For example, even for a9lh users, it tells them to remove RedNAND and do their life on SysNAND. Which is a choice the user could have made but no, here, there is no choice. And of course something who knows what's going on can say "oh ok, well no, I know Luma supports RedNAND, and even emuNAND, so for safety reasons and compatibility with my Gateway I'll keep an emuNAND" but a noob won't think. He'll just follow the guide. And get a SysNAND-only a9lh configuration when a RedNAND menuhax configuration may have been enough.
The "problem" is that this guide is the most up to date and the best written guide, so that's why it gets posted everywhere. But I agree it could use some formatting here and there, so that people can stop after menuhax or so that they can keep their RedNAND at the end. Otherwise, it'll get posted everywhere and indeed make the a9lh SysNAND-only configuration a religion.
PS: For the people who don't know me, I have a9lh on all my 3 systems so don't call me a menuhax peasant.
You can call me an emuNAND peasant though, but don't tell me I'm stupid for being "scared" of Nintendo because I'm not, I just want to be able to fiddle with my main NAND the way I want. I could even wipe it completely without rendering my system unusable since it's just my emuNAND.