RaiseEventAsync with a given taskhubname is missing compared to in process

In the non isolated worker model you could trigger an orchestration instance from a different taskhub like so:

Task RaiseEventAsync(string taskHubName, string instanceId, string eventName, object eventData, string connectionName = null);
See: https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.webjobs.durableorchestrationclientbase.raiseeventasync?view=azure-dotnet-legacy#microsoft-azure-webjobs-durableorchestrationclientbase-raiseeventasync(system-string-system-string-system-string-system-object-system-string)

I currently don't see any way to do that currently. Also an option to create a new DurableTaskClient dynamically for a different taskhub is not trivial as far as I can see?

    [Function(nameof(WebhookHttpTrigger))]
    public async Task<HttpResponseMessage> RunAsync([HttpTrigger(AuthorizationLevel.Anonymous, "POST", Route = "MyWebhook/{taskHubName}/{orchestrationId}/{requestId}")] HttpRequestMessage req,
        [DurableClient] DurableTaskClient client,
        string taskHubName,
        ILogger logger)

I would like to create a DurableClient with the taskHubName parameter given in the http route or RaiseEventAsync with a taskhubname as we could do in the non-isolated case. As far as i can find the only option is building a custom binder? Using binder as in https://github.com/Azure/azure-functions-dotnet-worker/issues/1106#issuecomment-1604982841 is also not possible in isolated.