I like the thinking, but I would stay far away from making it a requirement. An MVB requirement can easily backfire if it becomes harder/impossible to experiment with lightweight applications because "let's have one small programme with a lightweight application as an experiment/pilot/demonstration" instead becomes "if we start even a small programme with a lightweight application, this will be leveraged to change every other programme, so it's a big decision not to be taken lightly."
I like the thinking, but I would stay far away from making it a requirement. An MVB requirement can easily backfire if it becomes harder/impossible to experiment with lightweight applications because "let's have one small programme with a lightweight application as an experiment/pilot/demonstration" instead becomes "if we start even a small programme with a lightweight application, this will be leveraged to change every other programme, so it's a big decision not to be taken lightly."