Command blocks fail to recognize their power state changed for 3 ticks

Partner Rank: 3
Verification builds: Public 1.7, Beta 1.8, Beta 1.9, 1.13.0.2
Summary: When any command block receives power, it fails to respond to that power for three ticks. When a repeating command block loses power, it continues to run commands for three ticks.
Use Case: Nearly every command block system. Delayed ticks can add up when separate chains are necessary. Swapping power from one repeating chain to another will result in a window during which both are running at the same time. Repeating chains run for too long and chains of all kinds fail to respond quickly enough.
Repro Steps:
1. Place a repeating command block: /setblock ~ ~1 ~ air
2. Place a chain command block following it: /say running
3. Place a redstone block on top
Observed Results: "running" is printed three times after a three-tick delay. Three ticks before it realizes it's powered, then three more ticks before it realizes it's not.
Expected Results: "running" is printed once on the exact subsequent tick after the redstone block is placed.
Screenshots/Videos attached: Yes, comparison of problematic behavior (Bedrock) and proper behavior (Java) as described in the repro steps.
Notes: This has never worked correctly and therefore is not breaking any content, but it is very troublesome. Content that, relies on this behavior, intentionally or otherwise, may break when it's fixed.