These vids were already made +/- 18 months ago, when the tracking issue first blew up. The lists contain probably 150 domains and IP addresses. It is a simple concept, but very time consuming. The safest approach, not just for Microsoft, but for security in general is to implement a default deny firewall policy. It is simple to do, but again, it's rather time consuming:
a) Lock down the firewall and then observe the firewall log to see what traffic is being dropped.
b) Perform a Who Is lookup on the IP addresses.
c) If you are OK with the traffic, add a firewall exception (AKA white list it); if not OK then allow the firewall to continue to block same.
You will capture MANY Microsoft IP addresses, so when performing your Who Is lookups, note that they will indicate the entire network block that the individual IP is part of. You can block entire networks at once with a single firewall rule.
The problem, as has already been mentioned, is that you will also end up blocking Windows Defender updates, as well as the OS system updates, as well as other MS services that you may wish to use.
You'll end up with a sorta chicken and egg situation: It's not safe to go online due to the spying, but if you don't go online you can't get security updates, without security updates, it's not safe to go on line, etc., etc., etc. ...
The bottom line is that if you can no longer trust your OS, then it is time to move on and get a different OS. Keep in mind that even if W10 is contained within a VM, so long as it has Internet connectivity, it will still dutifully report on all of your activities as well as any data that it can observe/access.
Using W10 is a Faustian bargain.