Create application(s) separately from updates publishing

I want to propose a button/checkbox/process to ONLY create/update applications, separate from the publishing of software updates to the WSUS catalog.

Although it makes perfect sense to create/update applications as part of a scheduled publishing service sync run, I see a use case to manage applications separately.

The key selling point for the Enterprise Plus license is to easily create base applications from the catalog with a few clicks. Love it! And so do our customers. But there's a process for the monthly updates cycle and ad hoc application creation does not nor should it fit in that process. The real bother is that every time we want to create or update an application, we also initiate the download of many software update contents. If, say, Adobe Reader DC gets updates 3 times in between two company-defined patching cycles, I only want to see those contents be downloaded and published once, at the time of our scheduled sync. Now it just uses bandwidth, storage and time when it shouldn't as all I want is to create 1 application. Which also happens to be last in the sync queue. It makes the quick creation of applications, well, not so quick :)

I may be making too strong a case just to ask for a separate application creation process, but I thought it could be useful to understand my thoughts behind it. Just to be clear, I do not question the application creation being part of the publishing service sync or to separate the two completely. Just an additional option to only create applications would be super-duper.