Collapse to Function is pretty handy. It would also be handy if we could collapse to blueprint. The most tedious part of migrating from one blueprint to another is recreating all the variables, functions, and macros. If that could be done with the 2 clicks of a mouse it would make project reorganization so much more efficient! 
Sorry, but why cannot duplicated the blueprint or used heridage?
Sure, you could duplicate the blueprint and then have to delete everything out of it you don’t want, not to mention changing whatever class structure it came with. That could be a significant amount of work by itself.
What is heridage?
sorry, spelling error, heritage.
You mean inheritance? You don’t necessarily want the new blueprint to be a child of the old.
Look, there are a thousand ways to do anything in blueprint. I am just pointing out that having a collapse to blueprint would take the collapse to function ability a step further and give people quick options to break apart their blueprints if they decide they need to better organize things.
I build everything on the event graph in working order, and then AFTER I have working code, I break down pieces using the collapse to function tool. This capability is great. I have now reached the point where I am thinking to myself that if I could collapse to blueprint it would save many hours of work and generally make it more likely that I would migrate pieces of code to new blueprints in the first place.
I see, sorry, because you wanna copy all I thinking that you did need inheritance.
If this can helped… I use a lot my own macro library, i create a macros for everything, and macros of macros, and macros of macros of macros. Soo when start a new Blueprint only put a few macros form my library and get a lot of funcionality.
But yes, agree with you that copy paste between blueprints need improves. Like generate new variables when pasted variables from other Blueprint.