I actually agree with the 98-100% a9lh bootrate thing, It tends to work most of the time but like every few weeks-months I get a black screen and have to hold the power button
Something is wrong with your setup then, a9lh is literally as reliable as booting the FIRM in the FIRM partitions (because it's literally in the FIRM partitions and happens during the process of booting a FIRM, so...)
a9lh is 100% deterministic. So unless your 3DS hardware is failing in some way, a9lh is (regardless of what you think) 100% successful. How successful it is at reading your SD card, however, is another question. If you don't believe me on this, here. the arm9loader/kernel9loader reads the OTP, hashes it, uses the hash as the KeyX and KeyY of keyslot 0x11, which then is used to decrypt the secret sector which contains more encryption keys. From there key #2 of the secret sector is used to decrypt FIRM, after decryption, FIRM is jumped to (this is all normal stuff that happens on every 3ds with the new 3ds FIRM installed) we take advantage of the fact that key #2 isn't checked and we change it, which results in FIRM decrypting to something different. We control this in a manner that executes an instruction that executes code in a memory area we can control. So how do we control it? Well, we take advantage of a "safety" feature. The 3ds has 2 FIRM partitions and if one is corrupt, the other is loaded. So the first partition loads it's arm9 code into RAM, then checks it. It's signature is bad, so load the new (smaller) one. They didn't clear memory here. So since the new one is smaller, we have our code in RAM and a way to jump to it. This is arm9loaderhax. So, if any of that fails (which is impossible unless external factors are present (like failing hardware or maybe a solar flare wreaking havoc on something)) then yes, a9lh failed
So yes, a9lh IS 100% reliable assuming the hardware is working correctly
