I don't understand the action recorder approach to life in general. If you want to do the same thing over and over again just keep a copy of the same file and change the parts you want to change with a macro etc.
In AutoCad you can change variables after recording obviously but that deals with simple geometry that doesn't always need to have a relationship. I can't fathom how similar would work in Revit?
Q) We drew these slabs with 1200 radius but now we want them all to have 1250?
A) Group a slab and place it at different levels
Q) We placed 20 columns now we want 25?
A) No answer, other than copying standard bays over.
Q) We want to change these single doors to double
A) Change the type
Generally you would end up with a mess at some point because the double door is wider than the single so is half imbedded into an adjoining wall.
Where you do see these things historically they are based on VBA macro recorder. They chose instead with Revit a long time ago to go with SharpDevelop since at the time VBE/VBA was being discontinued by MS anyway and doesn't support .Net languages. Still all these years later and VBE is still a part of MS Office. I think MS at some point realised they just could not get all those old office macros written in VBA translated to a .Net version (they didn't want to force the issue so gave up on the idea of updating/discontinuing VBE). I think around the same time VBE was being 'discontinued' Autodesk added their version of macro recorder to AutoCad and made VBE an optionally installed component to AutoCad. Also people talk of running journals but what is a Revit journal? A VBScript file with a load of comments.
Here is a real idea you can ask for in ideas section:
Why can't we have the same sketch linked to multiple slabs in parallel???
That would be simple right? Since you have a database record for the sketch linked to a database record for the slab. You just need to enforce a check to ensure the elements are concentric on plan. When the slabs are moved out of alignment a warning is produced and the user can choose to have the slab item assigned it's own copy of the sketch (or cancel).
Less sketches = less sketch lines = less clutter (win win).