This sounds much more like you need an escript rather than a release…
Anyway, I asked something similar recently in the distillery slack, and I have been pointed to custom commands and told that I should start the application from there and do a lot of glueing…
And all I wanted was a single flag to indicate location of the configuration file if non-default…
I was able to convince higher instances to use an environment variable instead.
Well you could make a self-extracting and self-executing file, easy to package that up. Or make a flatpak or snap, or a docker instance, or all kinds of things.
Remember the BEAM is made for making distributed servers, not little single-file commandline tools, things like python/ocaml/C++/rust/go and so forth are better for that (but are all pretty bad at making distributed servers).