Your protocol should self-repair from a transfer error without a need to reboot the slave. Only if you reconfigure the slave, could it possibly be advantageous to request the slave to reboot to let the change "take".

In case a slave needs to be rebooted because it is hung, then any serial protocol will not help you. You will need to do something involving either a watchdog reset (if the processor has an internal watchdog) or do something externally that activates the reset signal of the slave processor.

But a transfer error should be considered "normal", even if the transfer error rate is expected to be way less than 1 in 1^12 bits. Transfer errors are never cause for a reboot.