ok, but do you really think they even test specifically for a9lh? such a tiny fraction of 3ds owners use a9lh... it doesn't matter that it can be quick to test for, but it would still take time and effort to make the test. we have no idea how and what nintendo does when they receive the faulty 3ds. maybe they test the integrity of the firmware, sure - but i guess they just turn it on.
If you think about it for more than a minute, the point is moot, really. First rule in customer support is usually: never believe what the customer tells you, check yourself. (This more borne of customer ignorance than customer malice, because most customers think they know better what's wrong when they have no clue at all.)
So when a 3DS comes in at repairs, it's placed into two broad categories:
1. Is hardware damage exceeding a certain level?
If yes, try to get it to turn on and system transfer to a new unit. If that's not possible, call the NNID guys to transfer all licenses from [Broken Console]'s serial to [Replacement Console]'s serial. Your 3DS lands in the trash.
2. Is hardware damage small / the fault not readily apparent?
Hook it up to your hardware diagnostics set and let it test all hardware functions while you fetch the replacement parts. Hardware includes the NAND storage, and you can bet your ass it will check it for data corruption. That's why we have two FIRM copies on the NAND at all, because they expect corruptions occasionally.
And what will they find immediately on a A9LH console? A corrupted FIRM image. (Since most of the NAND is encrypted and the FIRMs are in plain text, it's really the only thing they can check quickly and automatically.) The FIRM partitions are the same across all 3DSes, so it's trivial to check it against a database of legit hashes. I wouldn't even be surprised if the diagnostics program would automatically overwrite the FIRM0FIRM1 partitions with a legit one when it's "damaged", as routine repair. They don't even need to know it's an A9LH set up, they just notice a partially corrupted FIRM on NAND and fix it.
So now you either get a completely new console back on the highest firmware, or you get your old console updated to the highest firmware, with the exploit "accidentally" removed.
Not much of a difference.