I may not understand your workflow, so perhaps my earlier reply is not relevant. Here is a scenario where my earlier reply could help. If this is not your scenario, then perhaps you could explain your scenario again.
Say that you have a SketchUp model of a box. The box is a Component, in SketchUp terms. You want to use this box in some other SketchUp models (e.g., a model of a shelf that has an instance of the box on it; a model of a table with a few instances of the box on it). Those other models (shelf, table) are stored as separate .skp model files. Store the box in its own .skp model file. This could be done by originally creating the box as a model by itself, and saving it. Or if the box was created within another larger .skp model, then select an instance of the box component within that larger model, right-click the box, and choose “Save As…” from the pop-up context menu and then write the box Component to its own box.skp model file.
To modify the box, open the box’s box.skp model file and make changes, then save the box’s box.skp model file to create a new version.
To pick up those box modifications within another model file (e.g., the shelf model file), open the other shelf.skp model file and select an existing instance of the box component. Right-click the box, and choose the “Reload…” item from the pop-up context menu. Using the file browser that appears, locate and select the box.skp model file that contains the box. As soon as that is complete, all instances of the box component that are in the shelf model (as an example) will be immediately updated with the recently-saved version of the box model. The Move tool is never used in this scenario. If there are 1 or 2 or 5 or 500 instances of the box Component in the model, all of them will update in-place with the recently-changed box model after the “Reload…” function has been used to pull in the modified box Component.