There are only two ways to tell somebody thanks: Kudos and Marked Solutions Unofficial Forum Rules and Guidelines "Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Just note that the data type of the queue going into the top input will have to match the original.
What might be relevant as an idea is a node which will change the label of a wire or allowing nodes like bundle by name to use the wire label instead of the source label.
a) The desire to do this still baffles me. You're tying a runtime setting to a compile time setting. That's a maintenance burden.
b) If you want to do this, there's a much MUCH easier solution. Just create a subVI to do the Obtain.
Call this and then wire the output into your Bundle node. It will have the name of the output terminal.
Alternatively, you could stop using the unnamed Bundle node and start properly typing your clusters with a typedef that actually defines the name of the elements instead of relying upon the ad hoc names that come out of upstream terminals. If you were on my software team and I were your team lead, that would be a requirement before you could submit code. The arbitrary names discovered by Bundle nodes on diagrams are useful for short hops like between producer/consumer loops on the same diagram, but you're working with what looks like one of the state machine templates, and making that more well defined is critical, IMHO, to both readability and maintainability in the other frames as that state machine gets bigger.
Declined for reasons listed here: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Queue-name-bundle/idc-p/3143309#M31099