Unfortunately not, there is not an out of the box control for detecting the name of the screensaver executable.
On Windows, if the registry location is consistent for where this might be defined, a User Defined Control (UDC) for Windows Registry Value Content might work.
On UNIX, if there is a configuraiton file with a consistent name in a consistent file path location, then the UDC for UNIX File Content might assist with the task.
Also, if your requirement is that the screensaver exectuable be of a particular version/executable, the UDC for File Integrity would allow you to snapshot that file (MD5, SHA-1, or SHA-256) and then confirm that the other systems have the same file/location.
I am interested in knowing how you check for this today? Which settings you check to confirm? And the applicability of the above three options. I can forward the information to engineering for review.