React Navigation navigate() queue latency under concurrent requests

When multiple navigation.navigate() calls are triggered in quick succession—such as from rapid button taps or simultaneous deep‑link events—React Navigation queues each transition promise, causing the total latency to grow linearly with the number of pending actions. This behavior is documented for React Navigation 6.x and can degrade perceived responsiveness in high‑frequency UI interactions.

The library currently exposes no built‑in option to bypass or debounce this internal queue, leaving developers to decide whether to accept the delay, implement custom throttling, or seek a configuration flag that would allow fire‑and‑forget navigation. The unresolved question is whether such a configuration exists or should be added.

Is there a way to disable or adjust the internal queueing behavior of navigate()? Are there any undocumented props or navigator options that allow concurrent navigations to bypass the queue? If not, what is the recommended approach for mitigating this latency without introducing custom wrappers?