After reviewing your question with both the pNode team and support team I’ve found the following:
The pNode was designed to allow for the most ease of use to users. Therefore, it will check on a regular basis that it is connected to Wi-Fi. If the connection is not detected then it will automatically start up a hotspot which will allow a user to reconfigure the Wi-Fi connection. This is done for two reasons. First and foremost is so users can move the pNode to another Wi-Fi connection with little to no issues. The second reason is to automatically allow reconfiguring in the event something goes wrong with the default connection.
Given that, the functionality of connecting to Wi-Fi is baked into the code. When you plug the pNode into ethernet that it should automatically default to that connection. The easiest and most full-proof way of disabling the Wi-Fi would be to configure your pNode as a vNode but this would require you to self-stake.
You could make it a vNode but keep with the same vKey but then you’d be limited to only checking the pNode via your local network. This would offer you the benefit of both having full control over the vNode and also keeping it funded stake.
What issues are you seeing with Wi-Fi enabled?