@jja
This would be true in a development and programming world, but not in PowerApps!
When you alter the underlying table of your Gallery, the gallery will re-evaluate its controls. During that process it will cause actions to occur that you would not expect.
So, the best choice is to avoid trying to program it and instead work with it as the table that it already is. There is no need for all the extra work to be done by you in designing your app to maintain an additional table.
However, the above said...when you are basing a gallery off of a collection table, you will want to just make sure that your controls are getting their default values from values in your collection...and that does mean making sure that the controls are reflected properly in the collection.
The only reason you need the collection though for the gallery is to be able to add and/or remove a row. That is because the gallery needs a table. The collection will serve as that and is flexible for add/remove. However, beyond that, when you go to work with the data in the gallery, just treat it like any other table (the table is exposed with the GalleryName.AllItems property).
From that table you have access to everything about the record in the gallery - including the controls in that row and the values of those controls.