In order to remote into a system with SSH via Powershell, both Powershell and ssh server have to be installed AND you need to add a subsystem command to your sshd_config file on every system you want to remote into.
Subsystem powershell /usr/bin/pwsh -sshs -NoLogo
Powershell 7.x supports ssh natively in powershell sessions, so when creating a new powershell session w/ssh as the connection type you just specific the public key with...
$My_Session = New-PsSession -KeyFilePath path\to\key.pem -Hostname <sshhost>....
If you open the Bitdefender control panel, under protections there is likely a setting to disable that. Making an assumption here as I don't have their product
It just be a simple toggle between building a debug or release vs. been that way forever in visual studios Set debug and release configurations - Visual Studio (Windows)
Opening RDP over the internet is a really bad idea, but you'd either want to setup a Dynamic DNS service or if you have a system always running at home you write a simple script to query any number of websites, get your public IP and send the email.
A better solution would be to setup a VPN...
I believe Microsoft removed the cmd file. I think you can just add the reg still and reboot for the same effect
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
Doesn't help your issue, but to be frank your traffic is already encrypted (that's what HTTPS does), VPNs don't really provide any extra security just privacy. The ISP you are on and the network operator won't know what sites you visit and that's mostly all you get.
With caveats a VPN won't...