You must have one huge bundle somewhere to package all those references. You cannot programmatically unbundle by name. There are a couple of other things you could do that might work, though.
First, if the only thing you need to set through the reference is the value, you could use the Set Control Value method (of a VI, using an invoke node) to set the value using the name of the control, since you already have that. This eliminates the need for the reference cluster.
Can you restructure your cluster so that it contains two sub-clusters, one containing the references for the booleans and the other the references to the numerics? Then you can use cluster to array, and loop through the array, checking the name of each reference until you find the one you want. Even better, do the conversion to an array once when your code starts up and generate an array containing the labels of the controls referenced in the cluster, in the correct order. Then, when you want to reference a particular item, you do a Search 1D Array within that array for the string, which gives you an index. Convert the reference cluster to an array and index out the desired reference.
Personally I hate dealing with large numbers of references after spending years dealing with an existing codebase that relied too heavily on them. There were two clusters passed to almost every function, one containing references and the other containing values. It was expected that the programmer would update both simultaneously but it was very easy to forget, and caused unusual behavior when the value on the screen didn't match the one that was being used for calculations. Since then I try to avoid structuring my code in a way that involves generating a huge cluster of references.
