First of all, I am thankful for your responses here! Nevertheless, I would appreciate if you would assume that (unless proven otherwise) I kind of know what I am doing, before telling me “you don’t know how to handle lists” or “your logic is broken”. 
My definition of ugly code:
Having to put in multiple nodes to fix things that Dynamo should right in the first place.
In this example:
The Reverse node does not work on all PolyCurves (already in the backlog for the Dynamo team). The workaround provided by THEM (so not my fault) when I reported this: reverse the order in the list (as you can read here):
So now the workaround wasn’t working for THIS example, which is why I asked for help.
The “ugly data” is produced by the Dynamo intersection node, when intersecting two sets of surfaces.
I need the points to be created on the polycurves to flow into the same direction, as I am building Polylines from them later. I am now going by the reversal of the order of some sets of points on the PolyCurves which I wanted to reverse.
Again, nevertheless thanks for the productive suggestions of the posts above.