PRTG is optimized to monitor the status of network infrastructure, and traffic. Application monitoring is not a focus of PRTG. Such flexible sensor would also not fit well into the existing PRTG sensor architecture, which uses static channel names containing scalar numeric values.
As you mention scripts, an extremely simple, not-remote capable script is outlined here. As PRTG does not do real-time monitoring, instead it scans only once every minute (shorter intervals are possible but not recommended for script sensors) even a more sophisticated version would not be too helpful.
This leaves you an option to do it the other way run: Locally on the terminal server, schedule a script which communicates with an HTTP Push Data Advanced sensor.
For sensors provided with PRTG, a more detailed generic process / service monitoring is not planned at this time, because we work on a lot of other features and sensors.