I didnt say it was running behind the scenes and would cause a brick, I said you (aka almost everyone other than the author) dont know what homebrew is doing behind the scenes... therefore anything you run technically could brick you... intentionally or not.
A bug in a homebrew app could cause a brick, its "behind the scenes" as you don't know exactly what its doing... you just take the authors word that its not doing something it shouldnt (or that they didnt miss a bug that would cause an issue).
And I wasn't saying specifically that his issue was Wifi, I was correcting your statement that you can get into recovery mode with a faulty wifi module, which you cant.
Even with hardware faults that cause no display, the drive light still blinks correctly. which this one isnt. therefore currently you cant class it as a hardware error as the nand clearly isnt flashed properly after his attempts to fix it. Currently this is where the diagnosis is stuck, until that is corrected assumptions cant be made.