It seems it's easier than you think.   Confession.  I sent the marked up screen (red) over to the programmer for implementation and the transaction list trick may have some code behind it but i don't think so.  I briefly tested it and was able to change it without doing any code.  The creator is gone. 

We did this on some screens like customer so that folks could add contacts and ship to's but couldn't change terms, or anything else.   You do end up with two screens but then you CAN restrict by access code on this window management screen. 

Turned off the tabs in red.  

So we have two screens.   The original is only available to admin.   The second restricted screen has no access code.   The transaction was added to display the choice to admin users. 

I'm an admin user so i get a choice of screens.   The non admin just go into YOBPC.

Easiest way to do this is as follow, on the standard window OBPS add an access code. Then create a copy of window OBPS, in the transaction column provide a value and add a different access code to that window.

Set the visibility of the banking details to 'No' on the copy window and validate it.

Access to either window is now governed by the access code set on the window and assigned to a user. Note: this only stops that section from being visible to the user, while still allows access to it for standard processes. Also keep in mind that this can be effected when patching.