Curious if you know the address of this table in $ee offhand. I'm relatively sure this was intended to compensate for "lost" high resolution interrupt counts.
I am thinking of adding that table, since it doesn`t exist yet.

There is only built in 16bit scalar at $12048.
It works like this. the scalar must be converted to ms. In stock case that is $510*0.015234 = 19.74ms
Now you take opti low res signal in ms.
The spark adder will look like this [19.74/low res signal [ms]]/2=spark advance adder
19.74/1=19.74ms[750-1520rpm]=1 degree/2=0.5
19.74/2=9.87ms[1520-2279rpm]=2 degrees/2=1
19.74/3=6.58ms[2279-3042rpm]=3 degrees/2=1.5
19.74/4=4.93ms[3042-3807rpm]=4 degrees/2=2
19.74/5=3.94ms[3807-4559rpm]=5 degrees/2=2.5
19.74/6=3.29ms[4559-5319rpm]=6 degrees/2=3
19.74/7=2.82ms[5319-6097rpm]=7 degrees/2=3.5
19.74/8=2.46ms[6097-6849rpm]=8 degrees/2=4
19.74/9=2.19ms[6894-7228rpm]=9 degrees/2=4.5

There is also some rounding on that numbers so there is no halfs.

Can we derive some lag info from this and convert it to 1 degree error vs time vs rpm.
Increasing the scalar can account for the lag but alot of people will freak out when they see 40 degrees at WOT.