Absolutely no problem
You can only learn from mistakes
What you are referring to as “ms” is the time in milliseconds the script takes per frame.
So yes, generally you want to stay as low as possible to provide the best user experience (and the highest amount of fps (frames per second)).
But it is never a problem to go higher if it is just for a certain action (like this open menu). As long as you are not actively using the menu, it takes basically nothing. Just when it is open, there are a lot of DrawCalls being made (and those are the main caviat as to why it takes so much ms).
e.g. any script that has a “Help Message” (the ones in the top left corner) will usually draw 0.01ms more than it would without the message. And that is just one message.
A single ContextMenu menu with a single option already has 6 DrawCalls and for every other option it is at least two more DrawCalls (depending on the menu item type).
If you would use a NUI (e.g. html/css/js), that will reduce the “ms” that is being shown by a lot. But that does not mean, that it is actually taking less resources. They are just being shifted to the FiveM “browser overlay”, which as far as I know, does not show up in the resource monitor.
This script now uses the Asset Escrow System, meaning you can download it from your keymaster website!
There is currently no encryption being used at all!