Interesting.
The parsys wasn't made with this in mind because the idea is to give the Authors the flexibility to move around the resources inside via a visual GUI.
The need sounds like you are creating pages and or other resources that you want displayed in a list. I can think of like blog posts or something like that.
I would suggest creating a component that has some back end functionality that will build out a list of the resources you are trying to display and then feed them in whatever shape or form you are trying to display them at to the front end component. Separate out the logic to collect the content/resources from the display of the content/resources. This is all assuming its a specific type of resource that is being placed into the parsys/container and not just any component the author has access to.