Regarding this topic, we have updated the 4 LC architecture documentation recently.
With OutSystems 11 some strong dependencies were converted into weak dependencies (one of the strong dependencies that became weak dependencies is Screens), so it really depends on the platform versions, I don't know how feasible would be to change Discovery to take this into consideration.
Discovery is a visual tool to help analyze, measure and understand how to improve your factory architecture. This being said IMHO validations around weak dependencies should be in place and shown as violations. Is for you to judge if violation is somehow ok, if you want to live with, or if there is anything that you may improve and measure the effort needed to fix it.
I am one of those that can live with cyclic dependencies, if there is one justification, if you know the impacts and aware of the risks and you know how to deal with it, why not? Is a project management/factory management decision. I have seen many bad decisions to remove violations and the workaround implemented causes more issues than the one that it solves (there should be more reasons for changing your application code, just because there is one orange alert in one tool should not be the only reason).