Nope. This is not just a user rights issue, this is also a registry permissions issue. Some older applications make frequent changes to the registry. Because the program runs with the user's credentials (which do not have the ability to edit the registry by default) it is unable to make the changes unless some tweaks are configured. You have already employed the easiest of the necessary corrections to this problem but you have another option that might open up the permissions for users (howeverit will NOT prevent users from installing legacy apps). This is the trade off. You want the apps to run you also give the user the ability to install them. The method you have not tried is the compatibility security template that can be applied using Security Configuration and Analysis Tool. This template will weaken the permissions on the registry, user rights, etc for the users group to allow legacy applications to work properly.
To prevent users from installing legacy apps you need to remove the tools they could run setup from. Or an alternative is to only allow users to run programs that you approve (Use Group Policy to do this). This is a lot of work. The easiest thing to do is get a more current version of the legacy apps so they will work on Windows 2000 without impacting security. However if this is not an option for you perhaps you can seek a third party method.