Personally, I can't think of a good scenario where you will want to make these two tables a part of a recurring full load ETL processes.

Actually in my initial design, the [dbo].[TableList] held tables that you wouldn't want to truncate, I just switched the design around, that's why these two example.

With that said, you will realize that in the article I stayed completely away from ETL architecture or DW design so that data removal is at the descretion of whoever is using the tool. I tried to design the package as a utility tool with a sole purpose of data removal in any scenario one may chose, leaving the responsibility of what to delete in the hands of the user.