table_open_cache creates same number of advisory /proc/locks. Is it worth it?

MariaDB table_open_cache generates same and excessive number of advisory /proc/locks that causes OTHER programs on machine to waste cpu power ("sys load") when checking for locks. Are those really needed/worth it?
Executing lsof command while there are 100k locks in /proc/locks (made by mariadb with table_open_cache=100k) takes 2 minutes.
I see huge decrease in "sys" load after reducing table_open_cache from 100k to 4k on graphs.