How to support multiple scheduler extenders implementing bind

General Discussions
1

Asking for help? Comment out what you need so we can get more information to help you!

Cluster information:

Kubernetes version: 1.23
Cloud being used: bare-metal
Installation method: kubeadm

I config kube-scheduler with two extenders

"extenders": [
        {
                "apiVersion": "v1beta1",
                "enableHttps": false,
                "filterVerb": "filter",
                "BindVerb": "bind",
                "nodeCacheCapable": false,
                "urlPrefix": "http://service1/v1",
                "managedResources": [{
                        "ignoredByScheduler": true,
                        "name": "resource1"
                }]
        },
        {
                "apiVersion": "v1beta1",
                "enableHttps": false,
                "filterVerb": "filter",
                "BindVerb": "bind",
                "nodeCacheCapable": false,
                "urlPrefix": "http://service2/v1",
                "managedResources": [{
                        "ignoredByScheduler": true,
                        "name": "resource2"
                }]
        }
]

they have different managedResources and also different binding logic. I expect those two extenders to work together in one cluster, however, the scheduler complains “only one extender can implement bind”.
according to the kube-scheduler doc, only one extender may implement bindVerb. In my situation, no pod will request resource1 and resource2 simultaneously. Therefore, binding is actually called only once for each pod if scheduler allows this configuration.
So, are there any ways we can run those two extenders together.(for example by skipping this validation)