I would move the Instance itself… just as I do now.
I’m not suggesting Instances be unable to move - I’m saying I don’t want the master object it’s instancing to drag it around like a pet on a leash, when I move the master. The instance should have it’s own unique transform, not an interpolated/dependency transform of the master.
Well, yeah - that’s what I’m doing, which means after I use master object/collection for modeling, I now have to do lots of housekeeping (can’t use it, because transforms inherit).
And in order to maintain some sense of normality, every collection that I intend to instance (now, some other time when you’ve changed your plans, etc), has to be created at world 0/0/0, so that the instance also inherit the proper 0/0/0 origin.
Now I’ve countless collections of objects all stacked on each other at 0/0/0, which means I have to show/hide/solo most everything if i want to make an edit.
I make another collection to store them all in, hide THAT collection from rendering - awesome, now the instances don’t render either. So let’s put the “hide original objects” collection into ANOTHER collection, and hide THIS one from rendering. Thank heavens that trick works…
It’s simply poor workflow.