Is L&D's Consensus Code Limiting Transactions?

L&D is an alternative Bitcoin implementation like an alternative to Bitcoin core but also has a lot of Bitcoin oriented logic that L&D uses. Even if your L&D node is pointed at Bitcoin D as it's like block source it might still be using some BTCD logic and part of that logic is how it parses transactions. The parsing in BTCD was rejecting this transaction as invalid even though it is a valid transaction according to the actual you know Bitcoin consensus rules. And so basically what happened is L and D would mark itself as it's not a synced to the latest tip tip of the chain or like sync would be false something like that. It seems like a pretty egregious