Thanks jcomm. I hadn't thought of monitoring the tables through the editor legacy window. Thanks for that tip. I get a lot of bashing from others at Avsim on this, but so far I cannot see any advantage in the new system over the FSX system. I don't have any bias either way - my work has always been based on "what works in practice" rather than "this is new so must be better".
Let me cite just one example. There is a roll vs aoa table in FS2020 which at the moment is not used by default aircraft. I can clearly see why. It is a very crude approximation of several legacy FSX parameters which when combined well, promote a very convincing wing drop and subsequent spin. I have used this method for many years and though it needs many hours of fine tuning it works. The default small aircraft do display a roll/wing drop at high angles of attack without that table being activated, but it looks so fake and artificial as though someone said "I know - when aircraft X reaches 15 degrees aoa we'll make it suddenly drop a wing". It is as subtle as a brick through a window.
In FSX/P3d you can combine dihedral/roll stability/yaw stability/roll moment vs aoa etc etc so that they provide a very persuasive wing drop and with other params a proper spin (where the nose "tucks under" the wing drop). At the moment the GA aircraft in FS2020 do not spin. It is fake. They actually enter a spiral dive and are prevented from going through VNE by another crude solution - the grossly exaggerated induced drag scalar. A proper spin is unmistakeable to the trained eye, but it isn't there in the default aircraft.
No doubt I will learn more and more in the next few weeks and might change my mind, but so far, the multiple lift points are just Public Relations, and I simply do not believe there is anything revolutionary going on. The tables as presented are nowhere near as flexible as the FSX air file offered. They have take away a lot of detail but added what appear to me to be pointless and crude tables, a classic example being your example of - controls_reactivity_scalar = 10 !!