I cannot asset that doing a lot of branch reparenting will NOT muck up the inner workings of TFS somehow. I can tell you that there is no way to remove the extra merge relationship from the target branch dropdown. I can also tell you that TFS has plenty
of issues dealing with renaming files (not the same as reparenting), particularly when files were renamed in TFS 2008 prior to upgrading to TFS 2010. If any one issue keeps popping up on my radar it is the challenge TFS has with renaming files, and / or deleting
a file and adding a different file with the same name.
I know of no specific issue with *excessive* branch reparenting. But then again, I was not aware of any problems with file renaming in TFS 2008 until they changed to slot-mode identification of files.
I work with many companies with branching requirements similar to yours. None have found it preferrable to do reparenting as a routine process. I would personaly prefer to proactively create an empty branch structure in the correct hierarchy over routinely
inserting brancthes through reparenting.
This is my preference, and as I said ealier, I know of no particular issues but cannot assert there will never be an issue. Since reparenting relies on baseless merges and baseless merges in themselves are to be discourgaed (deletes are not handled as you
would expect, etc), I would not go this route.
VS ALM Ranger