Is KBupdate viable for Offline Win10 PC's stuck on v1703?

[BenK-JCom]

First of all, thank you for putting out such awesome content and being a community MVP!

The air-gapped systems I inherited are very far behind on updates. All the repo's mentioned only go back 30 days, so I have doubts that this will get me any required patches in-between. I had tried patching manually from the Windows catalog, but all 10GB of updates I tried throwing at it said they were not compatible with the system, so I started looking for a better scanning solution and discovered KBupdate.

2 Questions:
Can I / should I change the repo to pull updates from the last 1000 days?
Since I am going to run this locally, is NuGet required on every system?
It doesn't seem feasible to install all the prereq software on every client machine (Visual Studio, ect...).

OS Version: 10.0.15063 N/A Build 15063 (version 1703)

Background (Why we didn't update or replace machines yet):
My org is running legacy software preventing us from making the big leap to Win11, so we are waiting for it to be compatible with our software, before replacing these machines. I am trying to pick up the pieces from a prev sys admin and get these updated in the interim. It has been a struggle because of how far behind they are on updates. I read that the redstone build is not compatible with WSUS (or anything older then version 1903). We have around 60 machines stuck on this 1703 version.