If nothing ends up showing up as a usable USBMS device (which happens, depending on the timing/extent of the damage), you're probably out of luck.
The Coward's Rescue Pack might have helped, but, then again, maybe not, because, even with a hard-reboot such as this one, that shouldn't have screwed things up to that extent (*especially* in the case of Python, since that doesn't even ever touch the rootfs, so, all MrPi did was mount it rw & sync it, which should be pretty harmless), which, to me, has a slight whiff of hardware wonkyness. That, and the fact that you never ever hit the 'Your Kindle Needs Repair' screen, too.
Unlike hard-rebooting during a factory update, which *will* definitely screw things up, most of our custom packages should be pretty forgiving, barring external issues. (Not that I'd recommend doing hard-reboots just for fun, but, in this case, shouldn't have torn the house down :/).
See what @knc1 will have to say about the hardware side of things,
.