Some numeric command line settings are not range-checked before being used arithmetically or converted to narrower types. This can lead to integer arithmetic issues or bugs.
Generally, users of Bitcoin Core are expected to not set nonsensical values for settings, if they do not understand it.
This is a "tracking" issue, because basically all settings are affected. Though, I am not sure how pressing it is to fix all of them.
@maflcko are you open to prs adding some checks? or should i open issues to discuss anything i do first?
I think when the issue is: My cat walked over the keyboard while I was starting Bitcoin Core and this resulted in "invalid" options, it could make sense to wait for some larger reason first. If the issue is something that a well-educated user may run into due to misunderstanding or if there are real reports, it can be fixed. I'd say it is a case-by-case basis for now.