JoeViking245

That helped a lot.  Thanks.
In Windows Explorer, navigate to your /emulators/mame/ folder. Rename the file mame0285.exe to mame.exe. (If you need some kind of 'reminder', you can create a text file called mame0285.txt that will sit right next to it.) In LaunchBox, edit your MAME emulator. To the right of Application Path, click Browse and navigate to and select your 'new' mame.exe. Click OK to save and close. Try the Download process again.

Exclude not. Add.  
 
Controller Support - Supports - Light Gun
Platform - is equal to - Arcade
Platform - is equal to - Sega Model 3
Platform - is equal to - Sega Lindbergh
 
When you have 2 or more Fields that are the same (e.g. "Platform") they joined with OR. 
So above...   Supports light gun AND is in the Arcade platform OR is in the Sega Model 3 platform OR is in the Sega Lindbergh platform.
 
My atypical setup:
I don't generally use/view Platform Categories (nor playlists for that matter).  What I've done with my lightgun games is created a platform Arcade Lightgun. In there are lightgun games I have setup for just MAME.  I simply filtered my Arcade platform for controller-lightgun, selected all and then bulk edited them into the new platform.
Then I have another platform called Arcade Lightgun Other.  In here resides lightgun games that use Demul, Model2, Flycast, LinuxLoader, PCSX2x6, CXBX Reloaded and JConfig.

 
Then I got real creative and made emulator badges so I can see on-the-fly what emulator the game uses.  (I moused-ever the red one to see which emu it is because its logo is not very clear)

 

Correct.  If I recall correctly, FB-Neo ROMs are essentially MAME ROMs (in that they use the short_name.zip filename format).  I never paid attention to know that FB-Neo also consisted of console games.  If those also use the short_name, then they'd be more like MAME's SoftwareList ROMs.  
Also, ColecoVision would need to be scraped as ColecoVision.  Sega Megadrive would need to be scraped as Sega Master System.  But it still wouldn't work if the filenames are the short_name. 
If the ROMs aren't in the short_name format (e.g. BurgerTime.zip vs. btime.zip) and the scrape-as is set to ColecoVision (in this example), then they would work.

You can't do it Platform view.  But you can get creative and do that in Platform Category view.
Create a Category called something like Playlists.  Now edit your playlists to all have only the parent Playlists Category checked.
To make it look like you're in the Platform view, edit your platforms to all have only Root checked.
Then in Big Box, select the view Platform Categories.  You'll now see everything attached to Root. Which if done correctly, will be all your Platforms and your new Playlists Category.
 
To help get all the playlists under just the Playlists Category, you can use the plugin below.  But to get all the Platforms under just Root, you'll need to do those individually.
 
 

Custom Fields are a Premium feature.
Even in Premium, they are not viewable in List View.  They can only be seen in the game details panel or when editing a game.  Though, there is a feature request to have them added.  Feedback - LaunchBox - Support Custom Fields as Columns in Game List View
 
The author of that 3rd party plugin is a very creative programmer.  As you discovered, the Custom Fields can be [creatively] added. But they cannot be saved in the free version. They would however be saved with a Premium license.
 

You could try this plugin.  Just need an accessible copy of your original Arcade (MAME Games) platform's xml file.
e.g. ../LaunchBox/Data/Platforms/Arcade.xml (from the other PC)
I presume it still works. It's 3 years old and has only 4 comments and 1 review. But they're all good and I'm optimistic.  

Downgrading (rolling back) instructions can be found inside here: Installing, Updating, and Managing LaunchBox - LaunchBox
 

For a 22 your old ROM set, I'm curious how many games are actually in there. 
Actually, I just looked.  There's 4605 ROMs.  Only 2492 if you take out the clones. And less than 50 of those require CHDs (which is higher than I thought it would be).  But compared to the current MAME release having 11,761 games, that's a lot more manageable.
 
For a non-merged set, that would work perfectly.
The main issue you run into with a merged set are the clone ROMs.  These are actually physically inside the parent ROMs. But the application path will point to the ROM filename of the clone, even though the file doesn't physically exist. 
This is where MAME knows to look inside the parent ROM file if the clone file doesn't exist. But LaunchBox doesn't know to do that.
So in step 2 of the process, LaunchBox will look for the physical files to copy. It won't "see" the clones and will tell you as much.  Which may not be so bad. As long as MAME knows what it's looking for when launched.
For step 3, I believe LaunchBox again look for the physical files and change only the path for ones it can find.
 
You might be able to do step #2, then for "step 3"... close LaunchBox and manually edit the platform's xml file, doing a bulk Find/Replace of the application paths (changing from the old to the new).
If you imported no clones, that should make it a lot easier.  If you imported clones as Additional Apps, you might still be [somewhat] ok. If you imported clones separately, you still could be ok.  These latter 2 using the might method.
However, this all depends on you being "aware I need to add the BIOS and CHD files later on" as that's the "next issue".  Not all games require a BIOS and/or Device file, so quite a few should continue to work [after "the move'].  Knowing which BIOS and Device files is a feat on its own. But yeah, could just copy them all into the new location and call it good.  LaunchBox won't/can't do that for you.
However you go about it, just don't delete your full set until you know everything's good. Which.. note step #2 only copies the files. So that'll help [just in case ]. 
 
When you think you got it all good and find that a particular game or 3 don't work, there's a plugin called MAME Tools that one of its features is MAME Troubleshooting that can tell you exactly what's going on (or not going on) with a particular game.  e.g. a missing BIOS or Device file or CHD and what file exactly it's looking for.

That location changed in version 13.21.  You can read more about it here:  Media Packs - LaunchBox
An alternate means of adding an image (preferred if adding just one or two) is to click the yellow + sign in the (right) images panel [of your 1st screenshot].

There was an issue with a release [about 2 versions ago] where the notification wouldn't show. It has since been fixed.
You can manually check for updates (which if you're on "that version", that's what you'd need to do) by clicking the 'hamburger' Menu < Help < Check for Updates...

It will only delete (remove) the "GAMES from your [LaunchBox] collection".  "Collection" being the games you have installed in LaunchBox. (I guess that can still sound confusing. )
It will not delete the ROMs from your computer.  UNLESS you check the box under Tools - Options, "Allow deleting ROMs when deleting games". This is un-checked by default.  Also, if it were checked and you went to delete a game or platform, a 2nd popup message will show:

The database is back up and running now.

Auto-Import works when new ROMs are added to the respective Games/platform_name folder.
Not only does it work for finding new games added to your existing platforms, if you place ROMs into a /Games/ subfolder for a platform you haven't added to your collection yet, it will import those as well.
LaunchBox adding the subfolders [for you] helps to ensure the [new] platforms are named correctly which, coincidence or not, also ensures proper scraping.
aka, with Auto-Import enabled, place your ROMs in their respective Games subfolder(s), LaunchBox makes magic happen.
Read all about it here:  Automated ROM Imports - LaunchBox

Fixed(ish).
Close LaunchBox Navigate to you /LaunchBox/Plugins/ folder Delete the following folders: Dolphin LaunchBox Integration PCSX2 LaunchBox Integration RetroArch LaunchBox Integration (Re)start LaunchBox

Tools < Import < Manually Add Game...
Ctrl+N
Right-click anywhere in the main (middle) section and select Add
Tools < Import < ROM Files < Single Platform, then select Add Files and navigate to the file.

Again, it's not an incorrect number.  It's merely a 'different' number.  To help with your endeavors, try this.  Hint: use the "incorrect" number.
https://gamesdb.launchbox-app.com/games/dbid/4538

In the emulators Running Script section, add to the beginning of it
WinWaitActive ahk_exe snes9x.exe send !{Enter}  
As for mgba, I've never used that emulator.

Pretty sure you can rule out the animation effect of the Disc images.  That's a fairly basic WPF storyboard animation.  May look impressive in code. But is essentially as simple for WPF to do as it is for it place text on the screen.  You could comment out those 2 lines in the 2 files having them and test from there.
But if you're seeing the same issue in BB between all WheelxGamesView views (e.g. You see it using Wheel2 and also when using Wheel4), that will rule out the animation being an issue.
 
To supplement the extensive testing you've done thus far, grab an N64 reference video, make copies of it matching the filenames of your Steam videos.  Move you original Steam videos to somewhere safe and place the 'copies' in their place.
Yeah, in this test, all Steam games' videos will "be the same video". But each game is accessing/loading a separate "file".  Hope that makes sense.
This should rule out or confirm that the Steam videos, original, converted, trimmed or otherwise are the underlying issue.  Which you may have deduced already and be a moot test.

Ok. So a whole different folder location. That's good.  Did you transfer the /LaunchBox/Core/ folder?  That would cause an issue.
May try only copying:
Data Games Emulators (if it's there) Images Videos Actually, you could just copy the entire contents of C:\username\LaunchBox\ into [an empty] C:\LaunchBox\.  Then run the 13.17 installer and point it to C:\ (as the installer will make it C:\LaunchBox\).  Double check updates are off. Exit LaunchBox. Delete the contents of the /Updates/ folder and "call it a day".
 
And it never said 'a new update has been downloaded, would you like to install it now'?  (Assuming it did) Even if you clicked No, at that point it will install it next time you open it.
If that message popup never showed, check and double check that you're actually starting the exe located in C:\LaunchBox\.

To help determine what's going on, in LaunchBox can you share some screenshots:
- edit your emulator (in LaunchBox) and share a screenshot of
     - the Details section
     - and the Associated Platforms section.
- edit [just] one of the games not launching from LB and share a screenshot of
     - Launching section

When importing a platform (or updating metadata and media) and selecting to add bezels, LaunchBox downloads the Bezel Project files and then places the bezels for [only] the games being imported, into their appropriate folder.  e.g. for MAME, they get placed in your /MAME/artwork folder.  Myself, I don't use them for the RetroArch systems I have. But imagine they go in something like /RetroArch/Overlays/../../  But that's just a guess (for RA).
So the temp folder/files is just that.  A temporary download to then "cherry pick" just the ones for your games being imported/updated.
 
Assuming 'your' best option is getting them from EmuMovies (which is the best option), the only other option I'm aware of is
Scour the internet for them (time consuming and most likely, a fruitless adventure) Look in the Downloads section (here on the Forums) Create your own

Oh, it's a Steam game?  What its Steam ID #?  (In the games Launching section, the Application Path should by something like "steam://rungameid/21130".)
Continuing with these Q&A's will help determine what's-going-on, why-it's-happening (hopefully) and give the developers and idea how-to-fix-it for this situation so other don't come across this in the future.
 
 
If you just want to do a brute force fix-the-dang-thing...
Save it with the game that's found Resident Evil 4 (2005) and the LBDB ID # showing as 7801 Exit LaunchBox In Windows Explorer Navigate to /LaunchBox/Data/Platforms/ Open Windows.xml using any text editor Search for <DatabaseID>7801</DatabaseID> Replace 7801 with 261464 <DatabaseID>261464</DatabaseID> Save and close the file Open LaunchBox Select [only] your Resident Evil 4 (2005) game Tools - Download - Update Metadata and Media for Selected Games When asked "Would you like to update games with existing metadata and/or media?" Select "Yes, download and replace all existing metadata and media" (the 1st option) Click finish to "grab the correct games data" Now you can
Edit the game Go to the Alternate Names section Select "Resident Evil 4: Remake" Click "Set Selected Name as Title" Click OK to save and close

LaunchBox does not dictate the controls used inside the emulator.  That's between you and your emulator.  But it does pass command-line parameters. Which is why I thought 'maybe' that could be causing the issue.
 
Test:  In LaunchBox, right-click a game and select Open MAME.  From within [standalone] MAME that opens up, load "the game" and check if P1B2 is working as it should.
If it's not working, [in LaunchBox] edit your MAME emulator and make absolutely sure that the mame.exe you're pointing to is the exact same one you were testing on, outside of LaunchBox.  This is actually an [unfortunate] common occurrence. But an easy fix.
If in that Test it is working, I'm not sure what to tell you.

Check in Controller Mappings.  System Menu < Options < Controller Mappings (or Keyboard Mappings if your encoder is set to keyboard mode).
Check what's mapped to "Exit". "Exit" closes Big Box.  Clear it (best option) or change it to something else.  Hopefully that helps,

Myself, I keep all LaunchBox images (that I want to store) checked. Then in the EmuMovies tab, select only the media that is not available from the LaunchBox Games Database.  Which leaves you with Manuals and Videos.