JLR IDS/SDD has impressive capability to diagnose problems and to help fix them. It scans all available control modules at startup, stores a copy of the Car Configuration File (CCF), allows editing of the CCF, displays Diagnostic Trouble Codes (DTC), allows monitoring and activation of nearly all module signals, provides pinpoint step-by-step troubleshooting, connector pinouts and control module programming.
The system, especially module programming, is designed to be fool proof. Or as was said of the military: "a system designed by geniuses to be carried out by idiots".
Module programming is restricted to "appropriate" modules as determined by "qualifiers". This arrangement selects the best software file for each module based on the module part number and vehicle specifications, VIN, etc. It is intended primarily to prevent errors and avoid "bricking" modules. The unintended consequence is to prevent the system from being used in a creative way, to add unintended software and/or modules.

Following the lead of Cambo and others, reverse parking camera has been added to my 2011 XK and replacement modules have been programmed. The camera addition is reasonably consistent with the vehicle. Changing the CCF to accept the reverse parking camera is not excluded by a qualifier. Likewise, programming replacement modules native to the VIN range does not run afoul of qualifiers.

Like all things computer, IDS/SDD is modular. Poking around with file explorer reveals the inner workings of this amazing tool. We can get the jist of various functions and even activate some hidden tools. Some files are easily read, others are not. Readable files include .xml, some of which contain "qualifiers". By editing those files, it should be possible to enable programming with "alternative" files that IDS/SDD does not normally allow.

An example of modules that may be nice to program with "different" software are PCM and TCM. It is said that XKRs have been "factory tuned" using XKR-S PCM and TCM files for increased power and performance.

My interest is in retrofitting blind spot monitoring (BSM) for a 2011 XK. BSM has been available in the XF since 2010 and has been retrofitted to non-BSM XFs.
(See TOXO's brilliant write-up of XF BSM retrofit.)
The techniques used to accomplish the XF BSM will not work for the XK because qualifiers prevent CCF and module programming.

I am currently working on edit(s) to qualifier(s) and other files necessary to enable BSM CCF changes and allow side object detection (SODR/L) programming.

It would be helpful to peek at .exml files too. If anyone has expertise in this area, your help would be appreciated.

best regards,
Bill