Those lights react to existing system in planes (I mean existing data types, etc). If the actual plane you fly doesn’t have these systems or they’re coded otherwise the lights might remain ON (or OFF) depending on their previous default state.
Unfortunately that’s still the best solution for now (I don’t suggest to dive deep into scripting and customize it for each plane) so if it doesn’t work for a specific plane and it bothers you just create a separate profile in SPAD for that plane from the current profile and delete these functions from the problematic announciators.
SPAD is very good to customize anything but it usually needs a lot more effort than basic, uncustomizable default drivers.