As of #23092, PathPatternParser allows custom separators - but the extractPathWithinPattern implementation, when extracting the path within the pattern of a matched route (see PathPattern::extractPathWithinPattern), does not take into account the configured separator and only uses the default, /.