max_locks_per_transaction v18

experts,
We are planning to database upgrade, and evaluate PGv18 as next new
major version. Based on new release notes, one question about, "Improve the
locking performance of queries that access many relations ".
new share_lock_table size is based on max_locks_per_transaction, our
production databases have 8k-10k connections, and existing PGV14 stable
running there long time. Is it possible to get a new GUC instead of
reusing "max_locks_per_transaction", so we can more flexible control on our
production environment, for example, we want to keep similar value as
existing "shared_lock_table" size related, and separate control of
"max_locks_per_transaction".

Thanks,

James