Delay In-Place Application Upgrade Based On Publish Date, Not Release Date

The Publishing Service currently has this option:

When a new version of an application is released, delay the in-place application upgrade by X days

I have the above setting configured to delay in-place upgrades for the app by 14 days (our turnaround for pilot to production on SOP updates).

Our team recently experienced a rather tumultuous issue with Cisco AnyConnect where the 4.9.03067 version (released February 9th) MSI installer was placed by our network engineer in the local content repository to start staging the update process through our test/pilot groups before deploying to our org.

However, because (I assume) the above setting is basing the 14 day delay on when the update was released by the vendor, the application in Software Center immediately upgraded in-place, which was available to production.

It might be my individual opinion here, but basing the delay off the vendor release date doesn't make much sense... Basing it off each our local publish date, however, does. Everyone has a bit different approach to schedules, and the latter allows more flexibility to an individual company's needs.

My request is this: Ideally change that option to the context of delaying the in-place upgrade X days from when the update is published in a given environment. Or, alternatively, add a context to choose between vendor release date or local environment publish date for when we want to start the delay before upgrading the application in-place. Is that possible?