The mempool is policy, not consensus
Nodes may choose different admission, eviction and replacement policies while validating the same blocks. A replacement normally targets the same sender/nonce slot and must pay a meaningful bump to prevent cheap gossip churn.
Nonce order creates dependency chains
A high-fee future transaction cannot execute while an earlier nonce is missing. Selection must reason about executable packages, per-account limits, total bytes and adversarial transactions rather than globally sorting isolated fee values.