I just wanted to add that more granular node level timings (as in Substance Designer) is a not as easy to gather as there are multiple stages in the process. RC geometry is not as linear as Designer Textures.
Maybe timing tools can be added but it will require deep analysis. Thanks for Your suggestion.
Anyway there is a hidden internal tool to see how many times nodes are evaluated. It is more for debugging RC bugs than RC styles, but might be useful in some cases.
Just set RailClone to seed "9999" and create "C:\tmp" folder. Then it will generate stats in c:\tmp\railCloneStats.txt file.