AZ Controller can't do something Cakewalk API doesn't provide (except rare cases when workarounds are possible...), and some activity can be just "too heavy".
Also AZ Controller does not have "own state snapshot". Even AZ Controller is not perfect
So:
* tracking changes for plug-in in focus is relatively "light", so "Speed Dial" (with memory) is possible:
https://www.azslow.com/index.php/topic,206.0.html But it does not save the mapping between Cakewalk reloads. Also it just remember "ACT Control", so after plug-in changing it will control something from Cakewalk persistent
ACT mapping for that plug-in.
* tracking all strip parameters is "too heavy" (there can be 100s of strips and each has many parameters). But if your projects are let say under 32 tracks and you want track volume changes only, you can monitor the first 32 tracks volume to detect "the last change" and then use it for "Speed dial".
Note that both ways are affected by automations, AZ Controller has no way to distinguish "manual" changes from "automation" changes. A kind of work-around is tracking changes when the transport is stopped and don't track during playback/recording. Obviously in this case you can't map during playback then.
What you are asking is almost "MIDI learn" in Cakewalk itself. Unfortunately Cakewalk has not implemented it reasonably.
----------------
In practice, "main stream" Cakewalk surface approach (f.e. AZ Controller Startup preset) is more usable then per-project mapping. The problem with the last is memorizing several different layouts... Way simpler to remember that "this knob controls focused track volume, and that controls Cut in focused plug-in".
For very special cases it is possible to create very special separate preset. It can be project specific and map plug-in parameters directly, not throw dynamic mapping. So it is possible to control parameters of different plug-ins then (f.e. knob 1 "HP Freq of EQ on bus 'Drums'", knob 2 "Makro 5 of Synth 2", etc.). AZ Controller allows reference strips and plug-ins by name/type respectively, so it works after re-ordering tracks / plug-ins and in similar projects.
-----------------
Mapping absolute position of current track was never required in practice, even in most sophisticated presets for AZ Controller. It is simpler to use "current + 1", "current - 2", etc. Or use WAI related reference. WAI can follow current (moving it when current escape pre-defined WAI block, there are example how to do this). Think of 128 tracks project... you unlikely will ever use 128 strips surface.
