skizzosjt

you can do it like that, by unchecking use emulator and entering in the command line manually. retroarch needs at the very least the core and the specific ROM/game passed to it. syntax would be like this. I added -f for launching into fullscreen too
"C:\path\to\retroarch\retroarch.exe" -L "libretro_core.dll" "C:\Full\path\to\ROM\ROM.zip" -f so you would select the retroarch EXE from the Application Path Browse button and then only need to enter the core and game and any extras in the command line parameter field. would really only need this in said command line parameter field because the path to retroarch is set from the Application Path field
-L "libretro_core.dll" "C:\Full\path\to\ROM\ROM.zip"  
You cannot since the ROM file would normally be declared in the field which changes to the Application Path. This means there is really no spot where the ROM file is stored anymore. So LB wouldn't be passing anything (empty variable) and emulator wouldn't load any game as a result. (FYI %romfile% is the built in LB variable, but it's going to be empty in this circumstance)
You need to type out the ROM file. Here is an example using relative path for ROM file. It was exact same path setup by LB by default when "Use Emulator" was checked

that's correct they don't delete off your drive, at least not by default. you can check Tools > Options in the very first General tab is a checkbox "Allow deleting ROMs when deleting games" to see if that is enabled/disabled

it's telling you the problem, you cannot save to the main config with an active override. so, turn off the override before saving! or make the save before loading any content, as in before making any override active!
think about it. if you could save to the main config with an active override, then your overrides become part of the main config. and that's not an override anymore because it's now default settings. it was designed like this to stop users from turning overrides into default settings.
you're clearly trying to save at the main config menu since you get that error message. which means you're trying to make vulcan used at a global level. not sure if you wanted it global or not so pointing that out. if you want it at whatever level your override is, then you just change the setting and then update the override. if you used core override then use save a core override again for ex.
 

this suggests you're not adjusting things in the correct menu. that is where you go to change how controllers operate. I would bet your encoder is set to keyboard mode rather than xinput or dinput, since if either of those were used you could utilize controller mapping settings. process of elimination then would suggest you are using keyboard mode
try the KEYBOARD mapping menu instead

.\Images\Badges
the one you're looking for is "MotionSupport"

LB will change the game directory for a platform to the last used directory during an import.....this is GREAT when you have a system/platform than can have all files in a single folder.
But for ones that have a folder structure to it, such as individual games going into individual folders, it's going to list it like you described. It's doing the same thing, changing the path to the directory that was used during import.
This is BEYOND annoying to me because I have a couple platforms that use files on a separate disk. So if I accidentally try to edit these platforms when the disk isn't connected LB just crashes with an error it couldn't write to the folder that is designated as the game directory
 
I have movies, TV shows, and lots of Windows based games on disks that are not on the same disk as my LB/BB install. So after I got everything imported I changed them manually to a relative path so it wouldn't give me that error again. Though if I were to add anything new to them it would end up changing to that directory that was used during import....then I gotta manually edit again.

 
Just showing this so you know where those link up. It's the game directory

 
 
So to answer your question specifically....there is nothing to worry about. You're situation is fine as far as I can tell because it appears everything you have is on same disk, so can always use relative paths. Mine issue is a little more unique and I don't think is same as your issue. But wanted to explain that it could lead to problems if you have stuff on separate disks and they are not always connected.