Hi Justin,
Consider naming your python file something else, if there is a built-in module called emulator this could cause trouble. It doesn't have to be named the same as the executable in which it will be activated. As for AppContext, I imagine it would determine the name of the currently selected graphical WIN64 window (on Linux it looks for the current X11 window title). So I guess that emulator.exe probably doesn't have a graphical interface, just a window pane inside Android Studio, and you would still see the Android Studio executable "selected".
You can add a command to verbally mode switch or enable / disable the emulator commands. Or print the app context information and see if there's any way to distinguish the main window from the emulator window.