You could create a script to update your first table and re-create the second one again, and send to the journal. It would be like an update.
It wouldn't link the second table to the first, though, just make a new, updated version of it.
I attached a table ("The table that gets updated") with a script to do this as an example. Just:
- create a new table
- add some text in a few rows of column1 for that new table (your new rows. I assumed the new rows would come from a separate table)
- call the new table "the update"
Then run the script "Update table, take subset and create journal" in "The table that gets updated".
It will update the first table with the new rows, creating a brand new table, then take a subset of the brand new table. Each step gets sent to the journal.
It should be easy to adapt the general idea of the script to your specific needs (just edit the script to see what it does).