A pretty minor thing, but I just noticed the dosbox.conf file. It looks like it came from an ancient version, probably 0.62 (over 10 years old!). The conf has changed over time. It has a number of things that are no longer used and is missing newer sections. While the depreciated settings will be ignored and the missing settings will revert to defaults, it would be good to have one based on official 0.74. Additionally you have the captures folder set to "f:\capture", which I assume is a folder on your development machine.
One thing that I do with my installers is to only include a few settings that can be changed with my config tool and a couple of things that I include so that the user can manually set if they really need to, such as output for PCs that don't like "overlay". DOSBox will simply use its defaults for everything else.
Here is a good generalized conf for SCI games. Cloudee will of course want to change aspect to false. The EXE would need to be changed to for the SCI1.1 template. I have machine included to make it easy to set it to Tandy for AGI games, but could simply be removed for Companion so it will just default to svga_s3.
SCI1-SCI1.1 is the era of the infamous timer bugs, which means for the affected games you would want normal core and cycles from about 8000 to 10000. It might be good to keep this at dynamic core with max cycles so any potential speed bugs in the developer's game might surface during development.
This conf has the captures folder set to the game's path. The default path is the local %AppData%\DOSBox\capture, but if the game under development needs write permissions there should be no problems with using it for the captures.
The cmd only needs:
"< path to your DOSBox >\dosbox.exe" -conf dosbox.conf
if it is run from the same folder. The exit command is issued from the [autoexec] section of the conf. No path needs to be set for the conf file if it is in the same directory as the cmd. You could include the additional -noconsole command to suppress the console window. You would of course not want to do this if you are using a debug build of DOSBox.
The way we are handling DOSBox from Developer is that it writes the conf file based on the settings the user can select from the options dialog. This can be done on a project specific basis. It has more options than my config tool that I include with my installers. A debug build of DOSBox is included in the "Tools" sub directory under Developer's main folder. This eliminates the need to take its path into account for running the game. It uses no cmd or bat file to start the game.