showler

MO2 wurde nicht ersetzt. Vortex wurde von Nexus Mods unabhängig von MO2 entwickelt. Es war jedoch der Entwickler von MO2, der Vortex erstellte, und er betrachtete es als Verbesserung von MO2.

Using the default deployment method the mod staging folder has to be on the same drive as the game.   The downloaded archives can be on a different drive.
However, since it uses links to deploy the mods rather than moving the files, it doesn't actually take up double space.  One file is real, the other is just a pointer to the real file.

There's three folders.  Game folder, mod folder (deployment folder) and download folder.
You've said "game folder" and "mod folder" but not "download folder".  The download folder defaults to your AppData folder on your C drive. Did you move that to the 4TB drive as well?

Yes, not connecting to GitHub will prevent you from updating certain features of Vortex.
But that's a result, not the cause.  If Vortex is connecting to Nexus Mods but not GitHub it's not a Vortex problem it's a problem with your internet connection.
Can you access GitHub with your browser?
Try a VPN.  If that fixes the issue then try contacting your ISP and find out why you are having trouble connecting to GitHub.

You need to install the version I linked and then install the newer version on top of it.
From what I could find the error you were getting was because the newer version was missing files from the earlier version that it needed in order to remove and update the earlier version.  Therefore you need to "fix" the earlier version by reinstalling it and then install the newer version on top of the now "fixed" older version.
 
edit: Also Pickysaurus is a staff member at Black Tree Gaming, the developers of Vortex.  He provides most of the installation support on the forum, though he can bring it to the attention of the Vortex developers if he feels he needs to.

You should have the Starfield extension for Vortex installed.  It's the extension that tells Vortex how to install the mod so that individual mod authors don't have to worry about it.

If you disabled the Tundra Homestead wouldn't that be a missing master for the Creation Club patch file?

To add to what ChemBoy1 said, Vortex can't detect file conflicts if one mod has the files in an archive (BA2) and the other mod has the files loose.  In cases like that you need to extract the files from the BA2 archive in order for Vortex to be able to choose which one gets installed.  Sometimes a mod will be offered in both and "archive" and a "loose files" version for this purpose. 
"Loose files" will always have precedence over files stored in archives if they are different versions of the same file.
In this case, however, since the one you want to have precedence is already the "loose files" version it appears that the problem is that the files are not actually different versions of the same file (meaning they have a different name or different file path so Vortex doesn't consider one an override of the other).  As ChemBoy1 says this is likely because NAC X specifically calls for its own LUT files and you would need to change that coding.  Or rename the Psycho LUT files to have exactly the same name and file path that NAC X is looking for.

Someone would have to make an extension for it.
The site hosts mods for thousands of games because simply hosting a mod/file is easy.
The mod manager has support for a few hundred games because actually managing the installation of mods for a game is considerably more difficult.

I've answered this question before so your search must not have been very thorough.
The extension for the Witcher 3 might also contain general functions for other games by CD Projekt Red.  They are contained in the extension for the Witcher 3 so that you don't have to update the entire program in order to get those updates.  They could make them a separate extension but what would that gain?  Also Vortex functionality is designed for a general audience, not just those who only use it for one game.
The option to delete extensions is mainly there for community made ones, which will never contain core functionality for Vortex.  It remains for ones that are important because occasionally deleting an extension and allowing Vortex to redownload it can fix a problem with a corrupted file.
Most importantly however is that all this occurs because absolutely none of it causes any problem for you whatsoever and it has several benefits for many other users.  

No, don't do that.
"Purge" your mods to remove all the links Vortex created from the game folder.
Use your store app (Steam, GoG Galaxy, MS Store) to move the game if you have one.
Go into the Vortex settings and update the game location to the new location and then to move the deployment folder to the new drive.  Let Vortex take care of moving the deployment folder until its done.
"Deploy" your mods again to rebuild the links in the game folder.
If you do any moving or copy/pasting of the mods while the links are still deployed Windows will convert them to real files and make a mess of things for you.

As long as the downloaded files are in your Vortex downloads directory installing the Collection normally should have it skip downloading every file that's already there.
 
Just make sure the Collection revision number is a match.

Yes.  It's 254 ESM+ESP files.
You might want to look into ways to make some of them "light plugins" or merge them.

If it works when you enable a VPN then the problem is on your end.  Either your PC or, more likely, your ISP.
Try contacting your ISP with the information and see what they say.

Same process, basically.  Purge your mods, use the store application (Steam, GoG Galaxy, if applicable) to move the game, update the location of the game in Vortex's games tab, Deploy mods again.
Pretty much the only difference is that you won't need to move your deployment folder since it will still be on the same drive.

Check your "tools" tab and see if there is a "loot" tool that has been added.
If you downloaded a badly made Collection at any point it might be trying to reference a tool that doesn't exist.

Actually, I just realized SKSE is even easier than that since it has a "mod manager" download button here on Nexus Mods: https://www.nexusmods.com/skyrimspecialedition/mods/30379?tab=files

Probably the unresolved conflicts are preventing deployment so there wouldn't be any files for SSEEdit to work with.
More importantly, Vortex can't see conflicts in ESM/ESP/ESL files, so the conflict is between asset files that are being overwritten.  SSEEdit won't fix those so you should resolve the file conflicts before worrying about anything in the ESM/ESL/ESP files.

Vortex can't "scan" for mods that are installed already.  If there are ESP/ESM/ESL files in the data directory then Vortex will show them in the Plugins tab, but they'll be listed as unmanaged the same as the game's original files.
There's an extension that will allow Vortex to manage mods from Bethesda.net or from Steam Workshop, but it's not automatic.

Presumably because they aren't adding any new features to Vortex.  Development has moved to the Nexus Mods App which will have native Linux support.

Seems there was an update.  Look for information in the Palworld forum here: https://forums.nexusmods.com/forum/9043-discussion/
You'll need to click the "join community" button in order to post.

Sure.  Just don't select any options to "delete archive" that might come up and make sure you don't delete the downloads folder.
You might want to double-check to make sure your download folder isn't in the "Appdata" folder.

This isn't related to Vortex, but I believe your question is answered here: 
 

Okay, so your issue there is that the people who maintain the Unofficial Skyrim Special Edition Patch ONLY support the latest release of SSE.  If you downgrade your game to a previous version you need to have a copy of an earlier version of the USSEP that you kept from before.
You can see that it clearly states that it only works with 1.6.1130 and above.  

They are both part of the "bundled" extensions that normally come with Vortex, but they both received a necessary update today.
When the next version of Vortex is released they'll likely drop back into the hidden bundled section.