Existing repeating command blocks no longer working in 1.16.210

UPDATE 03/17/2021: Unfortunately this still isn't fixed for me.

Summary

Hello, I have searched the existing issues and can't find anything similar to mine.  For some reason, since version 1.16.210.50 RTX beta and now the newly released version 1.16.210, all of my hundreds of various repeating command blocks that are set to "Always Active" and contained a "/testfor" or "/execute" command are not working.  I can't seem to find any documentation with this as a known issue or not.   They have all worked prior to this.

I have done some extensive troubleshooting on my own and have discovered that it is only affecting my existing "Always Active" repeating command blocks with those commands.

If I create a new "Always Active" repeating command block and add a /testfor command, it works fine.

I went to one of my existing mechanism made up of several different combinations of repeating and impulse command blocks to troubleshoot, and discovered that if I change the repeating command block to "Needs Redstone", exit the command editor, re-enter the command editor, and change back to "Always Active", that block starts working again.

That means that I'd have to go across my 10,000+ square block map to find (if I can even remember where all of my hundreds of different command blocks are) and individually change the existing blocks to "Needs Redstone" and back to "Always Active".  That's extremely tedious and frustrating.

How to reproduce

• Load any world with an existing "Always Active" repeating command blocks with the "/testfor" command that were created prior to the last 1.16.210.50 Beta and 1.16.210 final release.

• Observe that the intended command is not occurring, and/or no redstone signal is output based on whatever command is executing on the repeating command block, such as a "/testfor" command

• Enter the command block's edit screen and change the redstone tab from "Always Active" to "needs Redstone"

• Exit command block edit screen

• Re-Enter the command block's edit screen and change the redstone tab back to "Always Active"

• Exit command block edit screen again

• Observe desired results are working again and redstone signal is now visible on attached comparators

Observed Results

Commands, such as /testfor @a[r=10] are not outputting any redstone signal when players or entities are within a radius of 10 on repeating command blocks set to "Always Active"  (nothing is happening)

Comparators are attached to the repeating command blocks with the command block arrow pointing towards the comparators.  

Expected Results

Commands, such as /testfor @a[r=10] should be outputting a redstone signal (visible on comparator) when players or entities are within a radius of 10 of the command block (or whatever coordinates are desired)

Closing Statement

Again, all of this worked prior to the recent (if not several recent) updates.

Is there any way that this bug will be corrected any time soon, if it isn't already something you're aware of?

Otherwise, I've been really enjoying the beta, despite the other issues that are still being worked on.  Keep up the great work!

Thank you.