Inkscape GUI and CLI Concurrent Document Access Latency

The goal is to understand why Inkscape's command‑line export operation experiences increased latency when the graphical user interface is simultaneously interacting with the same SVG document. Both the GUI and the CLI access the document's internal representation through a shared singleton object, and the GUI's rendering loop acquires a lock that the CLI must wait for during zoom or pan actions.

Observed delays are roughly double for a 5 MB SVG in Inkscape 1.1.x, while version 1.2 introduces asynchronous document loading that reduces but does not necessarily eliminate the contention. Factors such as CPU speed, storage latency, and background load can affect the measured times, and it remains unclear whether the lock can be made fully concurrent or if a runtime configuration can prioritize export over GUI updates.

Does enabling asynchronous document loading in Inkscape 1.2 completely remove the lock contention between GUI and CLI?

Is there a way to configure the singleton to allow non‑blocking read‑only access for export operations while the GUI holds a write lock for rendering?

Can the export pipeline be decoupled from the GUI singleton without breaking existing extensions or scripts?