There is no feature for introspecting the status code of other frames in the transaction. Edit: actually, we do have that, using TXPARAMLOAD (0x15).
You can also check for a revert by inspecting the effects of the frame. But performing multiple SENDER frames is equivalent to a single SENDER frame that batches the calls.
It should not be possible to make the entire transaction invalid after some SENDER frames have already been processed. So the only way this could be done is by adding a preamble to each SENDER frame that asserts whether the previous frame reverted, and make the current frame also revert in that case.