The gcloud command you are using is to create TPUs along with VMs. AFAIK, there is no script to detect the preemption of a TPU similar to the preemptible VM shutdown script.
In the preemptible TPUs documentation, you can see a note in the Detecting if a TPU has been preempted part.
Note: If your Cloud TPU is preempted, you must delete it and create a new one as described in Managing TPUs.
I believe that a non-native option could be to monitor the preemption of your TPU with some cron job or with Cloud Scheduler to delete and create a new one on preemption (eg: with a Cloud Function). Cloud Composer could also be considered.
You could also monitor the preemption from the logs (resource.type="tpu_worker") and create a log-based alert.
Additionally, in case your concern is related to the 24h preemption counter, you can reset this 24-hour counter with certain actions.
In the Preemptible TPUs documentation you have information on how you can create TPU Preemptible nodes, best practice, like described here.
Lastly, if your concern is not related to this 24h preemption counter and the reset actions workaround doesn't fit your use case, then I suggest you to raise a Feature Request on issue tracker.
I hope this helps
Best regards,