all preset are basically one step phaser.
For clarity, Presets can have any number of phaser steps, they are not limited to only one. (That may not have been what you meant, but I just wanted to make sure you didn't get confused later on if that's what you thought.)
List Cue ("Which cue name?")
Yes, this is definitely still planned.
If you just need minor tweaks (e.g. moving the "White" colormixing attribute to be immediately next to "Blue"), you can move them in the Attribute Definitions in patch:
ListRef only shows information about object dependencies, not attribute data. For attribute data we need a Search functionality. What are you looking to achieve in this case?
Clintos case in point... 
Some object properties are just settings. These use the syntax "Set <Object> Property <propertyname> <propertyvalue>"
Some object properties are references to other objects. These can use the syntax above, but they can also use the syntax "Assign <object> At <other object>"
Assign MAtricks x At Sequence y Cue z Part a.b
Recipes are children of Cue Parts. So a = cue part (default part is 0) and b = recipe line in that part.
That's all fair. 
In any case, I'm sorry to say that I've completely side-tracked your original question, which I sadly don't have an answer to.
Use Lua to make a macro and then trigger it?
To each their own I guess. ¯\_(ツ)_/¯
The following are my personal opinions:
I am attempting to as much as possible remove the use of Macros entirely from my workflow and move most needs to Lua.
Out of curiosity, why?
In the MA3 command line you can use single quote inside double quotes, and vise versa.
Nothing has been implemented yet regarding ASCII import (could in theory ASCII import into MA2 and then convert to MA3). However, it is now possible to record DMX Input. Dimmer Curves and Multi-Patch have also been implemented.
I recently had moving lights, where the Color Wheel was in Color.1 but the Speed in Control.3...
MotorSpeed for all attributes is pretty much always under the Control channel anyway. Unless you're talking about some other type of speed control.
I'd love to see an abstraction between Fixture Types / Attribute Definitions and Encoder Bar configuration. [...] Having the ability to define Encoder Bar layouts would be fantastic!
Yep, that's the plan.
That video is from before v1.0 was released. In regards to the complete encoder customization, Luke was talking more about a concept for how it could work. This topic is still a goal but has not been fully realized yet.
To be clear, the problem is not locking the user - the problem is locking the userprofile.
(MA International software support and Lightpower software support are essentially one and the same)
Up to you. In general I would recommend reporting any issues you find or feature requests you have to your local distributor.
Locking myself out with a two letter command should at least prompt an "Are you sure?"
In my opinion that is addressing the symptom, not the underlying problem. The problem is that the "Lock" keyword defaults to your UserProfile when you don't specify another object, rather than defaulting to either nothing or the selected sequence. I don't want a confirmation prompt with every lock command.
It looks like typing 'Lock' and then pressing enter locks the UserProfile, which is wrong in my opinion. If anything I would expect it to lock the Selected Sequence. This has been reported.
