Easier for who? And for what? I have written dozens of apps and drivers on Hubitat and SmartThings over the past 4 years and just cannot understand why people think they need these advanced constructs. Re-think your app. There is nothing that you need to create on this platform where you need to have absolute thread safety and deadlock protection. It's no different than SmartThings.
Re-think what it is you are trying to accomplish and design your app to fit the platform.
That statement is indicative that you probably should spend some time reading the documentation. The methods installed() and updated() are called by the system when the user first installs the app (clicks Done in the UI) or goes back into the app to update settings (clicks Done in the UI). Those are the entry points where you will need to set your event subscriptions and schedules. That method is called and the UI is not released until either installed() or updated() runs to completion. So yes, putting any kind of mutex protection on those methods or anything within them, could hang the UI indefinately.
Again, don't take this the wrong way, but before you worry about these advanced constructs, you should familiarize yourself with the basics of designing apps for this platform.