My understanding of how the remote repos worked was an item is only cached after it has been fetched. So if you’re setting up maven remotes you only see items in the tree that have been requested and I assume python works the same.
Local repos you should see all items in the tree though.
What is odd is how artifactory doesn’t appear to indicate what is being cached for p2 repos. I don’t know if this is because the p2 site is a composite site that combines multiple so it isn’t actually caching anything.
We have wandered out of my experience here, but I think I saw in another comment that your use case may be more needing a local proxy with centralised control of the KNIME update site access. So if there is a bug and it’s not caching but always ‘pass through’ maybe it still meets your need?
Might be a question to raise with JFrog support (I think this is a pro only feature so presumably you can raise a ticket with them)