Make digiline pistons pull an exact number of nodes

[FeXoR-o-Illuria]

Currently it's only possible to pull nodes with digiline pistons in one of 2 ways:

1. msg = retract_sticky retracting the extended piston and pulling exactly one node (even if there are more consecutive adjacent solid nodes in that direction).
2. {action = "retract", allsticky = true, max = n} pulling nodes only when the number of consecutive nodes is at most min(n, 16) nodes otherwise just retracting itself.

(Other methods won't pull which is fine)

IMO it would be terrific if we could have the behavior of 1 but with n up to 16.
Syntax could be similar to 2 with sticky = true as a flag or alike.

[FeXoR-o-Illuria]

I have a hard time imagining what "allsticky" is useful for so maybe even just changing the behavior of 2 would do?
(I am aware that moving nodes has kind-of a rat-tail of moving metadata, timers and alike.
However, this would allow to build e.g. a mover which builds e.g. stairs behind itself with deployers - similar to digtrons with their builders ;)

EDIT: I actually have a build where allsticky and the proposed sticky behavoir would make a difference.
(Pistons pull out cables of a nuclear reactor where the core needs to be dug for allsticky piston to actually do anything.
This is a setup to automate corium production without losing the core node and placing a wrenched core to dig the next round.
Could also be done with sticky behavior but a tiny bit less secure.
And this is really an extreme edge case I think x)

[SwissalpS]

you can create corium without destroying the core using node breaker - just for your info