Is this a viable method for remote office code reviews?

Example working concept [1] would be comparing "old" K&R C / C89 vs. port to "modern" C.

aka Virtual chalk board in VR 2 or 3D to support video conference.

[1] "Old C code -- how to upgrade it?" https://news.ycombinator.com/item?id=30957273#30962540

Concept example: Given "old" c code line of : (--(char)hash_ptr.parm.v.p) = fpop(sst);

A) "traditional method": run it through the compiler/debugger, "compile/debug/pray resolve all issues)

B) Advanced method:

   Assuming the license terms on the working binary allows decompilation;

   1) Use a disassembler to psudo C on the original binary and same hardware.

   2) Diff the resulting pseudo source code to see where things get interpreted differently.

   3) Then use combination of "tree differ" ([2]) and 
      compiler explorer to review the "differences", ([3])

   1) open source decompile to pseudo-C 
      software: ghidra [4]; retdec [5]
      compiler ware: gcc -fdump-translation-unit or clang -ast-dump

   2) Then use something graphbiz's dotty in conjunction with [6] nicst's tree diff util.

   Almost verything but the VR aspect,

   Non-free software for non-vr space ast idea:  http://www.semdesigns.com/Products/DMS/DMSToolkit.html

Resources:

[2] ast tree diff utils : https://github.com/syntax-tree/awesome-syntax-tree

[3] compiler explorer : https://godbolt.org/z/v4TdvE83b

[4] ghidra: ghidra-sre.org

[5] retdec: https://github.com/avast/retdec

[6] nicst utils : https://github.com/syntax-tree/awesome-syntax-tree