if you need something like macros which do more than one task, you should think about your code and consider refactoring instead.
A function should only do one thing (SRP-principal) and if you had stuff like you wished for it would go strictly against clean code style.
Next is: that a function should be as small as possible and should do exactly like it is called (never do more stuff like your function´s name suggest)
So in the end its better to have more functions with less lines of code, than one function with a huge amount of code/or blueprint nodes.
As for the question:
why do you need something like Select float? Instead, you could do something more readable like this:
And for the future:
if you can read your blueprint function from left to right, only reading functionnames and you are able to understand to workflow. It is probably clean code you´ve written 