Thanks for the nickname. I'll use it proudly.
Now show me this alleged confirmation of the "bomb" in the firmware. And please don't quote others as fact. That's hearsay.
Even if the hackers decompile all the 1.8 mb of code included on launcher.dat, de-obfuscate the decompiled code, highlight the codes that does the bricking job, explains how it works, most people - some commercial programmers included - won't understand what's happening there. It's low level programming that we're talking here, direct access to some controllers included on 3DS.
Algorithm wise it can be as simple as:
Check launcher.dat checksum
if checksum not equal expected checksum
go to end
if checksum equal expected
start 3ds_sys_menu_hacking routines
...
if( random_time and checksum for a portion not expected )
give eMMC controller size = 0
zero eMMC from pos_1 to pos_2
end-if
...
But the actual implementation will never be as simple as this, and maybe because of this, the launcher.dat file from gateway is bricking consoles, because it's not simple, and some bugs or situations escaped from the gateway's testers radar. And I'm trying to think about the bright side of this bricking code situation.
Also some of the "others" that found the bricking codes in gateway files are actually people that handles these kind of programs - console bricking codes included - from a long time.