To compare all the timings. It looks like this was done though and I have my answer. A small mini app delivers 250ms in comparison to 350ms using the ML app.
Cobra has a motion lighting app you might try.
Recall - my tests were done while my HE had lots of other apps (and RM rules) running. So I would hesitate to make any specific conclusions from the times I've noted (for ML and @asj's Pluggable Lighting). However, the broad conclusion that Pluggable Lighting is faster than ML is accurate.
What I am comfortable saying is that using Maker-API + Node-RED consistently yields the fastest motion lighting automation I have quantified.
So I tossed together Node-Red and the hubitat plugin which uses maker.
Motion lighting is around 200-220ms.
If you use this Lutron Caseta integration for node-red, you'll shave another 30-50 ms off that.
I'm going to take a look at this.
Stupid question, I have it set if motion is inactive to go to a delay of 4 mins, and then to tell the light to turn off. If the function (don't know my terminology) becomes active again would the delay cancel?
In general, I use a stop-timer node to stop the sequence when motion is active, and it restarts when motion is inactive. Here's an example
To avoid derailing this thread, I suggest following up on the node-red nodes for Hubitat thread.
Have you tried lovelace animated backgrounds? The animations change based on the status of Dark Sky weather entity. It's pretty awesome!