Does it create any issues for you? This should only happen if your custom expression can actually still be parsed as a simple wildcard rule.
If you have logical conditions like OR, or if you are using operators like equals, contains and so on or functions like regex_replace(), you should still see the custom filter expression view normally.
Yes. The non-standard http ports don’t redirect (8082, etc.) properly with the wildcard rule. I ended up creating a second condition (or) and it no longer replaces the custom filter and includes the non-standard http ports.