First off: The web console is optional, you can package your own war file with ODE by adding all jars into WEB-INF/lib and adding the ODE/Axis2 related servlets to your web.xml. Of course, some of the resources like config files are needed by ODE, but you don't have to include all HTML/JS/CSS/JSP files.
Regarding the deloyment it depends of your context and usecases. While the hotdeployment provides an easy way to deploy process models, you need to manually take care of versioning. If you however use the deployment API (a WSDL web service), ODE will take care of the naming conventions for process versions. If you want to deploy process models remotely, I'd recommend this way. If you want to ship ODE with predefined processes, I'd go for the hot-deployment approach.