I’m not very familiar with how Nilesoft Shell works internally, but I have an idea/question.

For example, take the native Windows context menu item Copy as path:

1. Hide the original Windows Copy as pathitem;
2. Create a new custom ItemB using item() in Nilesoft Shell;
3. When ItemB is clicked, directly invoke the original Windows Copy as path action itself
   (not reimplementing the behavior, and not using commands to simulate it).

One reason I’m interested in this is that the order of native context menu items is often uncontrollable. Also, some third-party menu items are implemented through DLL-based shell extensions and parameter passing, which makes them difficult or impossible to reproduce using commands.

So I’m wondering whether it’s possible to hide the original native item and create a Nilesoft Shell "proxy" item for it instead. From Explorer’s perspective, it would still behave as if the original native menu item had been clicked directly.