Klipper’s basic development philosophy is to only include features that really provide a meaningful and mensurable impact (see Feature idea: bed temperature loss compensation - #21 by koconnor).
Personally, I very much agree with this approach, since not all what is possible also makes sense. On the contrary, it might generate a burden in documentation, support, code maintainability etc.
Especially for support it is not uncommon to ask for a sliced gcode file, e.g. to see if macros or similar stuff is doing something weird. Alone from this aspect this feature, in my view, is creating more disadvantages than advantages.
In the same sense, diagnosing, if the slicer is doing something “bad” is quite impossible when using this format.