Nice! Official patch is out for some time now, I have also updated Airio to be able to read layout data and possibly compare them to some fixed values that must be used for the layout track to be recognized as "official", with personal records, online world records and all. I've debugged many things, but almost surely I overlooked some others.
Now concerning the layouts, I would suggest the following: Let's concentrate on the ones that have PTH files ready and that can be now directly supported. These are A11, A12, A13, A21, A22, A23, B11, F11, K31, K32 plus all their reversed versions. To check layout, I intend to hard-code the positions of check points (splits) that must match with expectation. So the positions of split lines and finish line have to be correct and never changed.
To be extra sure I think also route checkers could be used? I do not have much experience with layouts, but if the route checkers are placed on some suitable places between checkpoints, Airio could also verify these and make extra sure the layout/track is valid. So I would suggest adding route checkers after every crossroad. Signs showing where to turn next and how far it is would be great to have for better orientation.
Then there's the question on B23 and B23R. As it is done now, it is not a track for racing but purely for stunts and crashing. Although I have the PTH file done, I'm not really happy about this track, it is not a rallycross alternate racing path, it is car and race destroyer. Fun, for a short time, but unsustainable for serious racing. My view. The option, I think, is to create barriers not allowing to cut the path, especially where BL2 joins with BL1 near pit exit.
New in LFS are extended clean lap checks that will be applied for all custom tracks. Specifically, going to ground (grass, it is the same check HLVC uses), touching wall, hitting any object. The ground check also presents problem for B23, at both places where the rallyx part goes to tarmac.