SSIS for/each loop to ETL tables across databases
If I was dealing with your particular scenario, I would probably end up building a "mapping" table that had the [SourceTable] and [DestinationTable] tables.

Then I would use that table as parameters that feed into a cursor which Selects from [SourceTable] and pushes the records to [DestinationTable].

Of course, this would only work if all of the columns are the same accross all tables (or if you do "INSERT INTO [DestinationTable] SELECT * FROM [SourceTable]" which I wouldn't advise).

Pros to 100 components: Modular, allows for less changes if only one or a few needs to be changed.

Cons to 100 Components: 100 components to maintain and change, especially if it's a small change that applies to all of them.