Can I suggest that this could be implemented through the 'PID Config'. (I only have the demo version of ScanXL at the moment, but have just purchased DashCommand and have read around that Scripting may be coming available in the next version ... I'll cross my fingers!)
All your J1979 stuff appears to be in the SAE structure for example, Script values in SCRIPT, and auxillary vendor data in AUX. I have no idea how Ford Enhanced items appear but I'd imagine there'd be another item (FORD would be my unimaginitive guess!).
To me, the creation of a CUSTOM structure would be a way to satsify this feature. Each member of the CUSTOM structure could consist of specifying the following:
* Protocol (CAN, ISO, PWM etc),
* The header, ie Module Addressing so we can query modules other than the PCM
* The query mode - Query By Offset 21, By PID 22, or by Memory Address 23,
* A response 'index' and 'length' - ie where to find the data we're after in the response, even in multi-line responses. The 'length' can help us find anything from bitwise values upwards. Which also means the 'Index' would need to be able to refer to individual bits.
* The scaling/offset, (or Offset/Mult/Div to keep everything in integers)
* The units.
That way if we know for ourselves what PID we're after through our own reverse-engineering activities for example, we could display it.
My application of a feature such as this would be to use DashCommand to display non-PCM data - such as undisplayed Auto Climate Control parameters, or visible display of Sonar Distance values from a factory Reverse Park Module for example.
With this CUSTOM structure in place, you could then access it through the Script API and do other things with it as well.