You have that in Service Studio. "Remove Unused References' should be done by developers and Tech Leads at least at the end of sprint.

And it won't fix indirect cyclic references as it means someone added something from modules they weren't supposed to look at. If it happened, the problem is bigger than having one wrong action somewhere.

Personally I think this idea is a better solution:
https://www.outsystems.com/ideas/13974/automatically-remove-unused-references-dependencies-on-deploy-to-next-environment/

@Nuno Reis, I agree with your point. The TL or Developer should regularly check this in Service Studio, but instead, they tend to address issues flagged in the AI Mentor to resolve them there. Displaying this information like 'Unused Action in Module' would be highly effective. 

Alternatively, I agree with @Daniël Kuhlmann's solution.