the shared process engine setup is the recommended way of using Camunda BPM if you have no requirements that speak against that setup.
With that said, you can of course go for the embedded engine setup (application managed). The module dependency would be eliminated by that, yes. But since there is a provided module that should fit your case, I would still recommend going this way. Why is that? Because besides other things, bootstrapping and managing the lifecycle of the engine is up to you then. If you go for Spring Boot here, you get a head-start for this of course. But eliminating the module dependency by introducing a lot of other new challenges seems like a bad trade-off.
As for the remote engine setup, this is recommended for applications that have specific security concerns or do not use Java but want to make use of the process engine. Since the engine is a remote service then, we recommend using the REST API to communicate with it. So you will probably be forced to rewrite a lot of your communication with the engine.
Hope that helps.