Actions on Objects versus Groups or Page Level

I really like the option in Actions to perform something on "This Object" so am wondering if using it often can impact performance (make course run more slowly, etc.).

One example is, I have a template in my organization that requires lots of typing - (two text boxes for each lesson - which adds up to 16, but there are other screens where these appear in addition to the lesson screens - I think it's just a total of 24, but to me, that's precious time typing these things over and over again! So, I have these empty text boxes that change to the lesson name "On Show" - "Change Contents" - "This Object" based on the _lesson_title variable. This method makes reusing these objects SO easy, thought that's why that function exists :) Using variables for one or two screens and the lesson titles doesn't seem to cause many problems but was wondering if there's a tipping point or way to overuse having many actions attached to the object rather than bundled in groups.

In this case, I'm speaking strictly of actions that control visibility or non-visibility of objects - nothing complex. Because my brain taxes easily after hunting for objects in the Action drop-down,* I like to use "On Show Show or Hide 'This Object' " for certain objects that are visible under certain conditions. And I'm not sure if it's best to make the object NOT initially visible and do an "On Show Show 'This Object' " - if - else "Hide 'This Object'" or make it hidden then show it under certain circumstances. Is there a best practice for this also? (if using the 'This Object' isn't bad practice).

I appreciate ANY insight anyone may have - thanks!

* I realize "drop-down" fatigue can also be improved by either naming objects with _, grouping them at parent / higher levels, etc. - but I'm a bit limited in terms of what I can and can't change on this template.