I was looking into setting up dynamic classes because I had no idea how they actually work, I was just re-using things that other people setup (such as the examples in the doc), and was thinking about a way to store additive keyframes.
I found that bpy.context.window_manager.operators[-1] gives access to the last operator used in the bottom-left window history thing. (you can also view more ops further back)
This is a new and holy **** moment for me, so I could be wrong on when/where/how I can use it.
I can access the values from it, as well as previous actions in the history.
I can also modify the values but the changes don’t update anything else by just changing them here. For example, multiplying the transform values here won’t multiply them on the object unless I tweak it in the panel manually.
bpy.ops.ed.undo_redo() can re-apply changes but tweaking values like in the properties panel, doesn’t show up here, and calling the op would have to be done carefully to not be heavy.
I re-looked into reading the Info window again after learning this, which DOES log tweaks but alas, it was another fail, though I did find the Console editor has a history property storing the text your run in it, which still leaves me with hope for Info.
edit: my hope’s gone.
I found operators that copy items from Info to clipboard, or puts them all into a textblock/file but they’re internal/C ops, that uses something like: ReportList *reports = CTX_wm_reports(C);, which I can only assume is only an internal thing, inaccessible via python.
My only option for the Info route is generating the entire history as a textblock, then reading lines from that.