Rainbow doesn't warn me when critical path length settings are different than expected

[cassidydotdk]

Do you want to request a feature or report a bug?
A quality of life improvement

What is the current behavior?
Today, it is possible for users (developers, usually) to change the Rainbow.config settings for SerializationFolderPathMaxLength and MaxItemNameLengthBeforeTruncation (presumably to accommodate for a long local root path) and forgetting that this setting needs to be the same across all environments and as such should never be touched locally.

If the current behavior is a bug, please provide the steps to reproduce.
Just change either of these settings without reserializing the repository. All sorts of item missing errors will occur, or cases of items not being serialized as expected. These issues are almost invisible and very hard to debug.

What is the expected behavior?
That Rainbow tries it's durn best to detect this and prevent this situation from going unchecked.

Please mention your Sitecore version, Rainbow version, and if also using Unicorn, your version of that too.
Any