Therefore every variable font with an SLNT axis should have an AVAR table for that axis, and ideally the check should check that the AVAR table for the axis is correctly compensating by rerunning this kind of script to compare the results against what's in the font.
Observed behaviour
One of the many problems with registered axes is slnt is not a true angle. https://twitter.com/axis_praxis/status/1253281903798636546?s=19 points out this can be fixed with avar table mapping.
Expected behaviour
Therefore every variable font with an SLNT axis should have an AVAR table for that axis, and ideally the check should check that the AVAR table for the axis is correctly compensating by rerunning this kind of script to compare the results against what's in the font.