I agree with my other colleagues' responses below. I'd like to add a few additional comments.

If we determine there is an issue in a hotpatch update that impacts our users we could potentially deploy another hotpatch update that fixes the issue and potentially will not require a restart. This also points out we could deploy more than one hotpatch update per month if necessary.

Here you go, Nishant. Hotpatch updates | Microsoft Learn.

Specifically: Automatic rollback of a Hotpatch update isn’t supported but you can uninstall them. If you experience an unexpected issue with hotpatch updates, you can investigate by uninstalling the hotpatch update and installing the latest standard cumulative update (LCU) and restart. Uninstalling a hotpatch update is quick, however, it does require a device restart.

We understand that reliability is a top concern when applying updates. Hotpatching is designed to minimize disruptions by applying security updates without requiring a reboot. However, if an issue arises, there are multiple safeguards in place:

1. Rollback via Uninstall – Hotpatches can be uninstalled individually if needed. After rollback, users can install the standard cumulative update and reboot the device to ensure they remain secure.
2. Safe Deployment Practices – Microsoft thoroughly tests hotpatches before release, and customers can validate them in a test environment before broad deployment.
3. If you encounter an issue, Microsoft Support is available to assist.