Wanted to follow up one more time..
I went ahead and am proceeding forward with using the asar extension for now. I wanted to mention though that you will run into one more issue if you do the same. When you open an asar, the process will lock the asar file. This will prevent you from writing to it, overwriting it, deleting it, renaming it, etc. You won't be able to do anything with the file until you reload the UI or restart the app.
To get around this, I made a Loading window that I open at application startup as hidden. When I want to open something, it will show that window and tell that child window to load any relevant data then close that window. I then listen to the close event on the window and when its closed, set a 1 s timer to open back up (hidden again).
Doing it this way will allow you to keep the loading and such encapsulated within that window (which is always good). By opening it initially and just leaving it hidden, it makes it where it comes up immediately when called instead of taking a second to load the view. That process for that child window will then have the asar locked. By closing the window though, that process is then destroyed then freeing the lock on the asar. Then it will auto launch itself again in the background so that it comes up immediately again the next time its invoked.