A a reseller I would like to be able to create my own specific plug-in 'sets' for my WordPress customers. Normally this should be done at this level, not by the 'top level' administrator.

Maybe it is possible to use the same tab and visualize created sets from resellers with an icon.

I would like to see the CPU and RAM usage by Wordpress applications.

I would also like to see a warning about slow php scripts, which would help to catch Wordpress plugins that use too many resources.

The Wordpress Toolkit utilities in Onyx are awesome, but it would be pretty cool it could also check currently installed plugins/themes(versions) against the WPScan Vulnerability Database https://wpvulndb.com/ or some similar service so that known vulnerabilities could be highlighted, or automatically forced to be updated...

By default, WordPress Toolkit creates instances with the same interface language as Plesk customer interface. Please consider adding the option to set custom default language for new instances.

It's a useful for me, to manage all my sites in one wp instance, using 3rd level domains, like mydomain.com, forum.mydomain.com, shop.mydomain.com, catalog.mydomain.com, etc.

The auto-update is great, but it is even better to exclude plugins from the auto-update. Some plugins breaks the site or plugins are customized.

It should be possible to use the WordPress commandline tool "wp-cli" via chrooted-shell.

I habitually rename my wp-contents directory for security reasons (as part of iThemes Security). As a result Plesk no longer recognises the Wordpress installations on the server, when scanning so I'm unable to take advantage of Plesk's Wordpress features.

Please could this be modified to allow me to specify a custom name for my wp-contents directory?

As you know, WordPress Toolkit can update plugins and themes installed only from WordPress.org. Paid plugins installed from vendors' websites cannot be updated using WordPress Toolkit.
It's not convenient to update plugins from WordPress.org in the WordPress Toolkit and log into WordPress admin dashboard to update paid ones, so please implement this feature.
Especially considering that it's possible to update both free and paid plugins in the WP dashboard (in the menu "Updates").

Add an option to WordPress Toolkit to disable wp-cron.php execution and optionally create a real cron job.
You would have to add:
define('DISABLEWPCRON', true);
to wp-config.php and than give the admin a choice to set up a cron job with custom times (e.g. every 10Min or 6h).

See: https://www.siteground.com/tutorials/wordpress/real-cron-job/

Possibility to log into wordpress in case of site was migrated from another server or for newly created site that is not resolved.
Currently to log into wordpress it's needed to add "IP site" to hosts file.

Is it possible to have an WHMCS module created exclusively for WordPress Toolkit, in order to allow clients to use it's options from within WHMCS's client areas?

Basically have clients don't leave WHMCS client areas and perform some actions from within their WHMCS client account (add new site if set multiple WordPress installs in hosting package, backup and restore, install let's encrypt ssl, activate/deactivate nginx, remove site, creati staging site etc...).

Allow service providers to set the number of wordpress installs possible for a client in subscription settings

Would be great to have WordPress plugins to be able to have restoration points on a plugin upgrade basis and not only for WordPress major upgrades.

This way, WordPress plugins can be managed individually with more control over them.

Currently the Wordpress Toolkit interface is a bit messy with all the Wordpress instances of you and your customers.
It would be great if there would be the possibility so that you can mark and filter for certain Wordpress instances. Marking with stars could make it possible that the most important Wordpress instances always appear on the top and can be checked for updates and security issues very quickly.

Allow reseller/customer to install wordpress (and maybe apps) via XML-API. (without APS / admin permission).