I've searched through our knowledge base and cases and I haven't been able to find this specific issue. This is the only workaround I could come up with.
Run a Full Asset scan against these machines then run a Software Catalog Report to see which machines have SilverLight 5.1.4 installed.
This will give you a list of machines that you can use to create a new Machine Group. The script (batch file) can be push to these machines to remove SilverLight using the Custom Actions feature. You can use this same Machine Group to install the latest version of SilverLight using a Software Distribution scan and deployment. Once SilverLight is installed, you can scan for MS16-020 and push it out if it is needed.
This is a bit complicated so I think it would be best to contact support and setup some time to get this setup. Feel free to reference this thread.