The behavior has been introduced by JENKINS-2745.
Currently, this behavior is being widely used, so the fix won't be reverted

Do you want to see only configurable jobs in ListViews.
If yes, you can just...
1) Create a view with permission filters you need
2) Make this view default in Jenkins global configuration

Do you want to see only configurable jobs in ListViews.
If yes, you can just...
1) Create a view with permission filters you need
2) Make this view default in Jenkins global configuration

I should have different default views for each Project role. I'm suppose that's not possible?

For me Anonymous user is deanonymised, when he's authorized.

Why not add user special user?

Probably the best solution here is to have 3 default user's by behavior than:
1. Anonymous
2. Everyone
3. authenticated

I understand the need for backward compatibility since 2008 so it's impossible to change Anonymous and authenticated names.
But probably it is possible to add user for real Anonymous case? Like that:
1. notauthenticated → is really Anonymous
2. Anonymous → is really Everyone
3. authenticated → is really authenticated

not sure if the name (notauthenticated) for not logged in user that I've suggested is good, but I hope you get my point

I don't get the requirement here. It's not security, as users can just log out to get read access to all jobs.

It looks more like a presentation issue, which should be solved by using View Job Filters plugin and a view with the User Permissions For Job filter.

I see no point in removing permissions granted to Anonymous. If Anonymous has more permissions, then a user can just skip auth and have them. So what's the benefit authenticated user having less permissions than Anonymous?

It's safe to expect we're not going to change this.