I know this question exists and has been answered, sort of, but there are more answers needed:

I'd like to know if there is a solution other than recreating the component.  Generally you want (in my opinion) components with a remote path of /<component name> so that when you load the component it loads all of the contents into a folder with the component name.  If the root path is '/', then it loads all of the contents into /, and thus if you have multiple components all with '/' as a root path, it tries to load all components on top of each other.  This obviously is bad.  The other issue that is created with a remote path of '/' is that some command line SCM does not work, especially the JBE.   The jazz build engine will not load a component from the repository that has a remote path of '/'

The default behavior when creating components if one does so correctly is to have the remote path be /<component name>.  This happens when one creates and eclipse project, populates it, does team->share project->jazz scm-> and then creates a new component in a workspace and associates the eclipse project with that new component.  I don't know what sequence of events my developers have discovered which incorrectly creates components with a remote path of '/' but it'd be nice to be able to fix this without recreating the component, especially in the case where the issue is found months later and thus the component has significant amounts of history.