Triggering on one tooth is easy, but typically needs some compensation for transitions. How bad is the measured timing lag on your system? The issue with only one or few teeth is little or no predictive timing, so the engine runs timing on last known rpm, instead of current rpm of this rev. At the rate of engine accelerations, timing can have substantial error. Sometimes called transitional timing. This has been a repetitive issue in years past, and curious how yours does with predictive or compensated timing?
BTW - you missed the point in your reply, that it's not who is first, it is who's code or hardware is licensed and how (OSFW & OSHW). This is why Speeduino code does some things differently than, say, MegaSquirt, or that it had to change logos some years ago. Not violating terms sometimes requires some creative approaches, but provides opportunity to do things better in some ways. Josh and the community members here have put a lot of work into it, we appreciate you honoring that, and that's the purpose of the licensing. We are not a free R&D support service for closed-source profit models. If not meeting Speeduino terms or giving proper credit or support, you need to develop your own methods and license those. That's the point.
Now back to the fun.