When people are conditioned into following guides blindly they are screwed anyway, so whether otpless is included doesn't really matter. The old versions are all over the internet so there is no stopping anyone from trying it if they really want to.
Would you rather they just jump in this without a guide and have a greater chance of bricking than without? Would you rather someone just jump into a jet and fly it around without having some sort of lessons (GTA V), or drive a car without classes? Guides are there for folks who can't afford to break things, and for safety. Researchers have done the work and figured out the best methods for getting successful results. The OTPless method has had random bricks, and they made the decision to remove it out of safety, and will bring it back when they have nailed down the cause of the bricks.
The CTR Transfer method has known reasons for bricks, and the guides explain very carefully what you must do. Anybody who doesn't read the guide or skims it is risking their systems more than those who read the guides completely. My first 3DS I installed A9LH to involved downgrading to 9.2 then 2.1 using downgrade cia files. Unlike some folks I know, I read the entire guide 3 times, and then I downloaded every file for every step to my computer before I even started. It was time consuming, took me almost 2 days, but I took the time and read the guide carefully, every single step, to ensure I didn't break my system.
Now the guide has less steps! It takes me only 2 hours to install A9LH. I managed to install it to 6 3DS systems over the course of 2 weeks. I think these guides are useful, and should be read very carefully, with disclaimers where there should be, and only have working methods with known troubleshooting points in the event something goes wrong. Random bricks are not known troubleshooting points, except to just say "You're screwed. Wah wah!", and nobody wants that.
--------------------- MERGED ---------------------------
Here's a hypothetical scenario:
You are given two choices. You can either Follow Guide A, which is shorter than Guide B, but there's an unknown chance of you getting a brick. There isn't any known way to stop it, so it's entirely up to chance you'd get it. You may get it, you may not. So far, the number of bricks compared to successful results are slim. Less than 10%. But again, we don't know the cause of the brick, so you're taking a chance you may not be able to afford.
Guide B is longer than Guide A, but all steps have been thoroughly tested and vetted. As long as you follow each step, and read them over carefully, not skipping anything, you should be good. If something appears to go wrong, we have steps to verify if it's a brick or not, and methods to fix it if it's recoverable. This guide ensures that the most likely chance of a brick is User Error.
Given these two guides, which would you take? The random chance of bricking, slim but out of your control, or the one where a brick only happens when you don't follow instructions?