Hi,
The default number of elements per page is dictated by the number of columns / rows you configured in the settings of the menu item.
So if you configure 10000 rows there for your table layout, you'll get 10 000 products listed on the page when you arrive on it.
So that's not really the problem.
The real problem here is modifying the MySQL query loading the products in order to load the ones your want based on your specific conditions. This can't be done from a view override since the data is already loaded by the point you reach the view file.
You could create your own view with a plugin, but I think that's overkill for what you need.
A simpler approach is to implement the onBeforeProductListingLoad(&$filters,&$order,&$parent, &$select, &$select2, &$a, &$b, &$on) event of HikaShop (
www.hikashop.com/support/documentation/6...reProductListingLoad
) in a plugin of the group "hikashop" so that you can directly inject the extra conditions you need to only get the products you want listed on the listing of products.
So you could configure a menu item listing all your products in a table with 10000 rows, then have a custom plugin add the necessary conditions to the MySQL query to only load the products you need on that listing, and finally, if you need to customize the look of the listing, you can use a view override of listing_table.php
Doing it like that will be way simpler than adding your own view like with do with the plugin hikashop/email_history which adds its own controller and views to the backend of HikaShop for the Customers>Emails history. This plugin was a proof of concept on the system we've added to HikaShop years ago to be able to add controllers/views from a plugin.