No, you got code clarity wrong. Code clarity in ABAP means using System Hungarian Notation and it baffles me that almost every ABAP programmer I talk to think it's not redudant to use a command such as READ TABLE on a variable called GT_VBAK(for non-abapers, G for global variable, T for table).
The only advantage that I see is that for the most part, every program will look almost the same regarding standard SAP tables.
I agree with everything you said, they did some pretty neat stuff! the problem is that they started getting things wrong(from the development perspective) somewhere along the way, not sure if due to backwards compatibility or due to massive lock-in's with their own technology.
SAP right now is making a move on cloud using SCP and as open source goes, openUI5 exists.
I don't have much to say about SCP, just that the company I'm on decided to not use it, basically because we don't see advantages and to avoid future lock-ins
About openUI5, I honestly dislike it, the most useful features of that framework are locked inside SAPUI5(a supersetof openUI5) and pull requests are managed by a branch of the company itself and they are pretty harsh on it. SAP documentation on it can be bad and is entirely biased towards deploying things inside SAP or SCP, which is pretty annoying
The only advantage that I see is that for the most part, every program will look almost the same regarding standard SAP tables.