Well, this is exactly what Klipper is about:
- The MCU only receive processed commands and executes them. The processing is done on the host
- If you want to access the “raw” steps before being send to the MCU then you need to do this via a host module
Imagine, one would send your controller steps that already “contain” Pressure Advance modifications because the host calculated them in and then your MCU code puts another similar modification on top. This probably would lead to pretty much unpredictable results.
As it stands: Klipper host calculates and Klipper MCU executes. Working around this basic philosophy probably is a bad idea.
But then again, I’m not a core developer, so I happily stand corrected.
EDIT:
To add: you might also greatly profit from the tools that Klipper is providing, e.g. the so called MOTAN tools that allow in-depth analysis of the motion commands that Klipper host has calculated.
This might come in very handy during your development and to see, what is going on. See for an example Regression in dynamic PA - #7 by dmbutyugin