Remove all "for each" conditions. They're redundant in this case.
Also don't forget that you're running many collision checks with "is overlapping", which is very cpu intensive. Instead, create your UI hierarchies directly in the layout.
That way, you can get rid of the entire hierarchy setup on runtime.
And you can disable "collisions" on all sprites. All this only helps for performance issues during start of layout though.
If you actually have performance issues when clicking the buttons, maybe try a different variant to animate your UI instead of "Tween".
All these checks occur only once at startup and do not affect performance in any way. The performance is affected only by the opening of the high score table with the behavior of Tween. It doesn't matter how to attach objects, in code or in the editor - it's the same thing!