Hi,
I'm going to chime in here because AFAIK the collection you're referring to is used to display parent/child relationships in a tree view. In a Utility scenario we use it for the technical object workbench for example. So why don't you simply adjust your customizing (or custom development), to read the right relationships in the first place?
Example: imagine you are displaying a tree view with the following structure:
BuilHeader
>> BuilHeaderAllRelationshipsRel
>>>> Is contactPerson
>>>> Is payer
>>>> Is Ship to
>>>> ...
Now if below the root business partner node you want to display the contact persons only, do not try to remove the entities for Payer, Ship to, etc. but change the relationship that is read and turn it into something like BuilHeaderContactPersonRel.
Regards,
Nicolas.