Feature summary
As I mentioned in the title of the notification prpopnunu improve the display of pages with inheritance protection, because with the current state of affairs it does not work properly. Examples describe the state on Polish wikipedia. However, the problem seems to be at the core of the MediaWiki software. In addition, I suggest adding a page config that deals with this issue, similar to 'wgRestrictionEdit' or 'wgRestrictionMove'.

Use case(s)
so this is how unprotected page look like (in Vector & Minerva):

and that's how protected page look like, in example on full protection level so i cannot edit it as editor:

You can tell the difference on a first glimpse that you are unable to edit page in addition gadget which displays padlock also know that page is protected.
This is where problems start. Look how looks like page on same protection level but protected as result of inherited protection from other page (this page is also editor protected but it is not affecting the test cause i'm editor and i can edit that page when it is not part of page with higher protection):
as you can see whole interface looks like i can freely edit page but that's incorrect when i try i see this:

As you can see i'm unable to edit page and system informs me only in one place. Lack of pageconfig flag causes that even gadget doesn't work properly. Why don't we make it look uniformly at a time when you can't edit the page?
In addition i will show you that system does inform you about protection properly in other situation:
when editing some page doesn't matter which and it contains protected module or template it is specified on used templates list:
as you can see highlighted modules are fully protected but when i open their pages they look like i can edit them.

I was curios whys sometimes that happens and other times protections are displayed properly on modules/templates page. Well answer is simple when templates page was protected manually everything works fine everywhere but again when is protection is inherited bugs are occurring:

Benefits :
The advantage of introducing the proposed changes will be the uniformity and transparency of the UI, such operation of the system misleads even experienced users like admins myself once asked someone to correct something on the page secured with inheritance, he did it but wrote me in the discussion to do such small things myself next time and not to bother the admins, but I could not do it because the page was secured. In addition, the implementation of the proposed improvements will enable the creation of better gadgets for displaying page security markings.