Purple screen isn't always caused by a bad cmd resistor, although cmd resistor is the most common cause of it on oled (since you solder to it). It only means the bootloader can't read from emmc and throws an error message. It could also be a corrupted emmc, shorted dat0, or even a dead emmc. Shorted dat0 won't kill the emmc chip, just need to remove the dat0 adapter and reinsert it properly. Happened to me many times before when I was reflowing dat0 adapters (like 1 in 3 installs, melted solder/flux will pull dat0 adapter in and if it's not placed precisely on dat0 ball it will short to nearby dat1), had to desolder emmc chip and reball. Finally gave up on reflowing and went straight for reballing instead.
My best guess is that you left the dat0 wire dangling around when you booted ofw and updated it. dat0 wire caused interference and corrupted your emmc. It happened to many people using badly designed picofly core style chips (the one relocates emmc chip), interference on data lines corrupts/bricks emmc.
If you don't have hot air station then your best bet is to reinstall the modchip, hope it boots to hekate, then you can do an emmc rebuild. Yes it's doable even with a dead/blank emmc, only catch is that the switch will be banned (not from nintendo's end but you lose prodinfo which holds all certificates needed to connect to nintendo server). Did it once before, the toshiba emmc was fried when desoldering, no idea why i used same temperature setting when doing other switches. Replaced it with a blank samsung one, modchip will write the payload to the new emmc and boot to hekate.