As long as you can do a "zpool status" and the bad drive is no longer listed before you plug the drive in, things are okay. That verifies that the disk is permanently removed from the zpool.
I doubt the broadcast storm had anything to do with it. What is likely at fault is the fact that the system spontaneously rebooted.
To be honest, if the situation had been different, I'd have wanted to get all of the disks sent to iXsystems for analysis of what actually went wrong during the reboot. Clearly *something* was totally messed up. ZFS should have gracefully recovered from the failed disk, but clearly didn't. I'm not sure exactly why. It could have been some weird behavior that was the reboot with the broadcast storm. I just don't know. If it had been a new pool with only test data I would have asked if I could get the disks sent to iXsystems. But I realize that home users are a little less than reluctant to mail off their personal data, let alone their zpool, to some company for analysis.
I'd say that if the scrub comes back clean then all is good again. ;)
I try to make it a high priority to remove any failed disk from the server whenever I can. It sounds like things went from okay to bad pretty quickly, so there may not have been much you could have done anyway.