Regarding the "Stop query when timeout" action, You are correct. Since, it is part of the actions to be performed after the plan condition is met.
I would carefully go through the [Resource Manager](https://community.denodo.com/docs/html/browse/7.0/vdp/administration/resource_manager/resource_manager) section of Virtual DataPort Administration Guide before setting my plan and rules.
In the scenario described, The memory usage could also be due to the queries that are in progress.
I would configure Denodo Monitor to get log details. So that I can associate query execution vs CPU usage. The logs are present in below location:
For Configuring the Denodo Monitor you can refer to [Denodo Monitor](https://community.denodo.com/docs/html/browse/7.0/vdp/administration/monitoring_the_virtual_dataport_server/denodo_monitor/denodo_monitor) section of Virtual DataPort Administration Guide which gives details for setting the Denodo Monitor.
If you are a user with support access and still consider that it is a potential problem in Denodo Platform, I would suggest you to raise a support case in the [Denodo Support Site](https://support.denodo.com/) with detailed logs, execution trace or VQL if possible for analysis.
Hope this helps!