Yes, it's pretty easy, even if you don't know anything about the compiled format. You just run the script in a debugger and catch when it uses the password for something. As a general principle, it's impossible to hide a password that's being used on someone else's machine. If they can run software that uses the password then they can see the password.
In this case, even that is overkill: since the password is passed to the
openssl command, all you need is to put a wrapper for
openssl that logs its arguments, or to observe the
openssl process while it's running.
In addition, it's likely that the password can be recovered from the encrypted file, by simple brute force, which will not be as long as it should be.
openssl enc is horribly bad at generating an encryption key from a password: this should be slow (see Possible to show Metasploitable (Linux) password in plain text?, How to securely hash passwords?) but
openssl enc makes it fast, and worse, you're not even using it correctly: you're using it without a salt. See How to gradually encrypt the tshark output file along the capture? for what to do instead.
A word of warning: from your recent questions, you appear to be well over your head when it comes to security. I strongly recommend that you stick to simple things and keep your system's defaults as much as possible. Your attempts to use tools that you don't understand to make unnecessary improvements tend to make things worse.