Which SpriteSortMode and batching approach minimizes CPU overhead for paginated large sprite datasets in MonoGame?

Goal: Render only the visible portion of a large 2D sprite world using pagination while keeping CPU overhead low in MonoGame’s SpriteBatch.

Constraints: SpriteBatch can operate in Deferred or Immediate mode, and its SpriteSortMode (Deferred, Immediate, Texture, BackToFront, FrontToBack) determines when and how sprites are ordered before submission. Frequent texture switches or per‑sprite sorting can erode batching benefits, especially when the visible set changes each frame.

Uncertainty: It is unclear which combination of SpriteSortMode and manual batching strategy (e.g., pre‑sorting by texture, using texture atlases, or limiting draw calls per page) yields the lowest frame time for a paginated viewport.

Does using SpriteSortMode.Deferred with a pre‑built texture atlas reduce CPU time compared to Immediate mode with per‑sprite texture switches? Which SpriteSortMode delivers the lowest frame time when the visible sprite count is limited to a page of 500 sprites? Is there a sprite‑count threshold at which switching from Deferred to Immediate mode becomes advantageous for paginated rendering?