So I really don't know why you won't let the users decide what and which plugin he prefers to cover this use case?
This is a change requested for Jenkins core, not about a new plugin. The trend has long been to move functionality out of core into independently updatable plugins, so rejecting new feature requests that are very similar to established plugins' features is consistent with that.
Of course I'm not the final arbiter on what goes in and what does not, so feel free to reopen this issue. But based on my experience, this will not make it in, as it is not actually a necessary feature (since it has adequate alternatives), and brings significant additional complexity with it.