I decided to revisit this to see if I could get this with ffmpeg. To understand what I did, take a look at this:
https://groups.google.com/g/video-downloadhelper-q-and-a/c/BzPLK2YyL-sYou'll probably want to bookmark that for easy reference. You'll want to read that entire thread, if not now, eventually. As you read through that thread, you'll come across 2 references to how to post a proper problem report. But I already showed you upthread here how to do that so that's not so important now. Another reference in there gives a complete tutorial on how to use ffmpeg. You can skip directly to the relevant reference by doing a string search on "cannot download" in there. That will reposition the web page on the relevant reference. Click the link that gives you & you'll find a complete explanation of what I'm showing in the rest of this post.
One thing I must correct. I didn't notice it yesterday but there are 2 variants in the VDH menu for resolution 1280x720. The first one, the one with the 5.1Mbps indication, is the higher quality one. The second one, the one with the 3.5Mbps indication, is the lower quality one. Same 1280x720 resolution, 2 different quality levels. If you download both of those, you will see the difference in quality reflected in the video properties, specifically the bit rates, of your 2 downloaded MP4s. I'll leave that to you as an exercise.
Back to ffmpeg. As usual, I looked for a master manifest. The usual practice on most web sites is for the first .m3u8 listed to be the master manifest.

Running ffprobe on the first manifest highlighted in that image showed that it was indeed the master manifest. I have attached the output of that ffprobe execution to this post. It describes 8 Programs, matching the 8 variants in the VDH menu. VDH analyzes the manifest, same as ffprobe does. You'll note that each of the 8 Programs found by ffprobe consists of one video Stream followed by one audio Stream. Each video Stream shows a resolution. You'll note that the resolutions listed by ffprobe are the same ones listed by VDH, which is entirely to be expected. You'll also note that the order of those resolutions in the ffprobe report is not the same as what you see on the VDH menu. Like I said, VDH sorts the resolutions in descending order. Since I mentioned 1280x720, you'll see those 2 variants in the ffprobe report as Program 2 & Program 3. Within the ffprobe report for Program 2, you'll see the indication variant_bitrate : 5095219, and within Program 3 you'll see variant_bitrate : 3490552. These match up with the 2 variants for those Programs on the VDH menu. This is not surprising. VDH gets this information from the manifest, same as ffprobe does. You would do well to retrieve the manifest itself & look inside it with Notepad or whatever text editor you are using. It is an educational exercise. I'll leave that for you to do at your leisure.
Looking carefully at the ffprobe report, I settled on Program 1 as the one I wanted. This consists of video Stream 0:2 & audio Stream 0:3. Accordingly, I executed this ffmpeg command:
"G:\ffmpeg\ffmpeg-2022-03-17-git-242c07982a-full_build\bin\ffmpeg.exe" -hwaccel auto -protocol_whitelist file,crypto,data,http,https,tls,tcp -i "
https://ga.video.cdn.pbs.org/videos/nature/7e61c729-5933-4376-897e-849fe10c8a75/2000070523/hd-16x9-mezzanine-1080p/lxsloze9_naat3605-16x9-1080p_983.m3u8" -codec: copy -map 0:2 -map 0:3 "Q:\VDH Testing\Nature.mp4" 1>"Q:\VDH Testing\Naturemp4.Err" 2>"Q:\VDH Testing\Naturemp4.Log"
Google has folded & wrapped that to fit here on the web page. But it is actually a single command line with no line breaks.
This downloaded the same video that I downloaded upthread using VDH. This time it showed the correct resolution of 1920x1080, unlike the weird 1912x1088 that VDH generated. The bit rates & other properties were the same. The size was once again, unsurprisingly, 2.46G. Surprisingly, this download completed in about 6 minutes. I wasn't paying attention to what Resource Monitor was telling me for this download. But the table napkin calculation gives an average download speed for this ffmpeg download of just under 7.4 million bytes per second. I have no idea why this download went so much faster. Maybe it's a function of the demand on the PBS web site now compared to when I did the download with VDH. It's just an interesting observation. Well, it's interesting to me, anyway. It doesn't particularly affect the results of the downloads.
I noticed in the ffprobe report an error message about subtitles. I have found that ffprobe always fails to properly handle whatever captions might be present. (Captions. Subtitles. They're synonyms.) I have no idea why it gives this error. Ffmpeg is always able to download subtitles if they are present. You just have to find them. To find them, I told the Network Monitor to filter for captions:

This turned up what I expected. I then downloaded those with ffmpeg:
"G:\ffmpeg\ffmpeg-2022-03-17-git-242c07982a-full_build\bin\ffmpeg.exe" -hwaccel auto -protocol_whitelist file,crypto,data,http,https,tls,tcp -i "
https://ga.video.cdn.pbs.org/captions/nature/7e61c729-5933-4376-897e-849fe10c8a75/captions/hENYtj_caption.vtt" "Q:\VDH Testing\Nature.vtt" 1>"Q:\VDH Testing\Naturevtt.Err" 2>"Q:\VDH Testing\Naturevtt.Log"
You can see in my ffmpeg commands that I named my output video file Nature.mp4 & my captions Nature.vtt. This allows VLC to automatically display the captions during playback:
