Implement mechanism to allow for the creation of scan profile out of the box during automated deployments

[enthusedcoder]

Describe the solution you'd like
So, really big fan of this application, as I have been using it personally for years, and when I demonstrated what it was capable of to leadership at my place of employment, they were also impressed with it as well and have expressed a desire to deploy NAPS2 as the scanning solution to all of the stores we manage. However, we like to lock down these remote environments so that they only have access to what they need and everything is configured and ready for use as to not confuse users at these stores, and the only aspect of the software that leadership is concerned about is that NAPS2 requires that the user scan for and add the printer that the app uses to scan (at least as far as I can tell from the research I have done), and it would be ideal if there was a way to automatically setup the scanner profile as part of an automated deployment,

Describe alternatives you've considered
So, rather than describe alternatives (not sure why you would ask it to be honest). I will detail how I believe my feature request could be easily accomplished using functionality that already exists within the app. Specifically, the command line interface or the NAPS2 sdk, but I will just stick with the command line interface for simplicity's sake. The command line interface already allows you scan for available printers and also allows you to specify a particular device to use for a scan as an argument when the --noprofile argument is also used, so I was thinking the command line interface could be modified in such a way that would allow for the "device" argument to called alone (or create some additional argument for scanner profile creation). The command line interface would then generate a scan profile that sets the device that matches the device argument as the default scanner for the profile and sets all other profile values to default (or you could get freaky with it if you want, but we can always go in and modify the xml values ourselves if need be) that the application will then use when launched. That is my suggestion.