I've realized that with the ability to reorder parameters, we can have a solution for these aggregate frames (!).
The reframer simply adds arguments to the end of the frame (like an AUGMENT) so the frame can be subsetted and still compatible with the reframed function. But then it adds the reordering information so its arguments go first.
Not only is it not far out of reach, this makes it seem like there is no such thing as REFRAMER...it's just ENCLOSE which doesn't do type checking until you actually DO the embedded frame. Basically it just becomes ENCLOSE/NOTYPECHECK!
This is pleasing. You aren't getting these "second class citizen reframer functions" which are limited in how you can work with them. It's pleasing in the same way that being able to add parameters to the interface of functions which have locals of the same name is pleasing. Once you put something in the domain of ACTION!, it has the properties of any other action with the same interface. Shades of monads. 
I'm tempted to attack this right now, but I'm in the middle of something else that is also really cool.