If a patch is superseded, but still applies, it should remain relevant and deploy-able.
As other have mentioned sometimes testing and version control can require the deployment of an older patch. Recommending or guiding to the latest patch set would be nice, but it should not remove the ability to deploy older patch sets, if there remains a business requirement to do so.
I agree that disabling the default remediation scripts on superseded content would be a good safeguard against accidental deployment, but retaining the ability to deploy the old content is essential.
Since MS17-010 remediation is part of why this is being discussed, an easier path to showing remediation of specific vulnerabilities or patches is a critical reporting component.
If asked to demonstrate that a system is patched for MS17-010, I should be able to without having to call out that I applied the June patch release instead of the May release. A potential solution for this is to include all rolled up CVE IDs in the subsequent patch content.
As of now, when I search for MS17-010 content in the Bigfix console, all I return is the March content. Worryingly I see systems that show relevant to the March content, but do not show relevant to CVE-2017-0143, CVE-2017-0144, CVE-2017-0145, CVE-2017-0146, CVE-2017-0147, or CVE-2017-0148 in the Vulnerabilities to Windows Systems site.