As is often the case, the devil is in the details.
Ostensibly, each table in the spreadsheet is distinct. It's possible to link data across tables, but there's no inherent relationship between them when it comes to number of rows, columns, etc.
The exception to this is Pivot Tables, which work to summarize a primary table, and these do scale dynamically based on the source data, but without knowing your use case it's impossible to tell if that would be sufficient.
The 'traditional' way of dealing with this is to oversize the child tables so they reference back to the main table, with error checking to make sure it's valid (e.g. if the parent/master table has 20 rows, you create a child table that has 40 rows, with the last 20 rows empty, waiting for the parent table to fill it out), but it's cumbersome.
There are no built-in triggers that will force an action on another table, but there may be external solutions. For example, it would be possible to craft an AppleScript that, when triggered, added rows or columns to all tables on all sheets, or maybe just normalized the sheets so they match the first sheet/table, or some such. There are many ways of approaching this, with lots of caveats to consider, but it might be the easiest long-term solution.
It all comes down to what it is you're trying to do, how frequently it changes, and what constraints or limits there are that need to be followed.