This is a follow-up for the issue reported in #1621.
PR #1714 fixes the problem only partially. The keyspace is read from the prepared statement, but the replica map contains information only for the default keyspace configured for the session. As a result, the code at policies.go:L615 returns nil, causing the query plan to fall back to primary-replica selection.
Impact: requests are routed only to the primary replica, even when replica shuffling is enabled, leading to reduced load distribution.