In some ways, OP’s suggestions are a recipe for building hostile teams! Why would I be entitled to interrupt someone to review my code, just because they are sitting next to me? Always on zoom? No, thanks. It invariably devolves into micromanaging. Constant KPI awareness? Most companies cannot even agree on how a valuable KPI looks like. Remote pair programming? Honest question here, is pair programming still a thing…
Pair programming isn't widely practiced for obvious reasons: It looks like you just made your code twice as expensive. There are studies justifying the cost by showing it can be recovered with less testing, code review, and bug hunting. But that evidently hasn't been persuasive. Also, anyone familiar with statistical quality control (SQC or SQA) would look at pair programming and see 100% inspection. Very suboptimal…
If, however, you see them as humans with different skills that can be shared amongst each other, then pair programming makes a lot more sense.