Virtual p2 repo does not work with remote p2 repo if remote domain does exist as "normal" remote repo already

A p2 virtual repo, that also includes a Remote P2 Repo, does not gather+resolve the p2 artifacts of the Remote P2 Repo, if the domain of the Remote P2 Repo is already added as a traditional Remote Repo.

Example:
Remote P2 Repositories: http://host/path/subPath/
Remote Repository (configured separately before): http://host/path/

As a result, if I navigate through the Repository Tree, and zoom in to the newly created p2 virtual repo, I do not see the p2 artifacts resolved+listed correctly, rather only all artifacts that can be found http://host/path/ (which are not p2 compatible, only those located in the sub directory are)