Wow, thanks for your very fast response. As you will see below, your suggestion worked. THANKS!
Unfortunately, there are issues with my attempts at ripping an ULTRA HD Blu-ray disc that surprised me. Please see below. Looks very similar to this on the forum:
"UHD Backups Stall at About 50%"
viewtopic.php?p=64037
One speculation is this happens when the process moves to the second layer. The OP is from Jul 14, 2018.
After a day of testing *my* working theory is anything with one layer works. Anything with two layers fails.
I will continue testing and let you know if anything happens that is counter to this working theory, *especially* if I ever get a two layer disc to work.
I should mention that the LG drive is *external*. It's in a Vantec NST-536S3-BK NexStar DX USB 3.0. It it attached to a USB USB 3.2 Gen 2 Type-A Port on the motherboard.
Note: I documented all of this because there may be something important that I overlooked and/or don't understand. This is all very new to me. The 11th generation Intel CPU (I9-11900K) forced my hand (loss of SGX support). My older system had an I7-7700K which has it and works with the CyberLink software. My new system doesn't. So, this looked like a promising workaround solution.
*** the flash update process
C:\Program Files (x86)\MakeMKV>sdftool -d G: rawflash enc -i f:\in\file.bin -v
Loaded SDF.bin version 0x7e
Reading input file f:\in\file.bin
Flashing flags = 0x0 : 0 0 0 0 : ---- ---- ---- ----
Sending image in encrypted format
Current Drive ID: HL-DT-ST_BD-RE__WH16NS60_1.03_212005081010_KLGK99G4150
Ready to write drive flash memory.
Type "yes" to continue, "no" to abort
yes
Operation started: Sending flash image to drive
100% Operation finished
Operation started: Programming flash
100% Operation finished
Done successfully
Command produced 0 file(s)sd
*** the resulting drive information
C:\Program Files (x86)\MakeMKV>sdftool -d G: --info
SDF.bin version: 0x007E
Drive Tool SDF present
Drive Specific SDF present
[Drive Specific SDF] Embedded Info Strings:
8000:LibreDrive Information
8013:Status
8105:Enabled
8001:Drive platform
:MT1959
8002:Firmware type
8107:Patched (microcode access re-enabled)
8003:Firmware version
:1.03
8005:DVD all regions
8100:Yes
8006:BD raw data read
8100:Yes
8007:BD raw metadata read
8100:Yes
8009:Unrestricted read speed
8100:Yes
[Drive Specific SDF] Embedded Status Message:
8099:Using LibreDrive mode (v%1 id=%2)
:06.2
:4083C4CCDB14
Identification SDF present
[Identification SDF] Embedded Info Strings:
8000:LibreDrive Information
8013:Status
8102:Possible, not yet enabled
8001:Drive platform
:MT1959
[Identification SDF] Drive autodetect string:
mtk:19:59:JB8 :HL-DT-ST:BD-RE WH16NS60 1.03:NM00600:-
*** MakeMKV's view of this. Looks promising.
Drive Information
OS device name: G:
Manufacturer: HL-DT-ST
Product: BD-RE WH16NS60
Revision: 1.03
Serial number: KLGK99G4150
Firmware date: 2120-05-08 10:10
Bus encryption flags: 17
Highest AACS version: 61
LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 1.03
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes
No disc inserted
*** Getting reading to read an Ultra BD. Looks VERY promising:
MakeMKV v1.16.3 win(x64-release) started
Using LibreDrive mode (v06.2 id=4083C4CCDB14)
Using direct disc access mode
Evaluation version, 30 day(s) out of 30 remaining
Loaded content hash table, will verify integrity of M2TS files.
Using Java runtime from C:\Program Files (x86)\Java\jre1.8.0_291\bin\java.exe
Title #00006.mpls has length of 5 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00005.mpls has length of 21 seconds which is less than minimum title length of 120 seconds and was therefore skipped
File 00000.mpls was added as title #0
Title #00001.mpls has length of 116 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00007.mpls has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00008.mpls has length of 8 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00001.m2ts has length of 116 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00011.m2ts has length of 5 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00010.m2ts has length of 21 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00013.m2ts has length of 8 seconds which is less than minimum title length of 120 seconds and was therefore skipped
Title #00012.m2ts has length of 10 seconds which is less than minimum title length of 120 seconds and was therefore skipped
DEBUG: Code 233 at kZiHFAlydMtxamzT9q3TOZjq:0
DEBUG: Code 233 at TPma1H8FyuBdxzBCA3b7cTP8:0
DEBUG: Code 233 at DZ2Cs6GdJHcOVItkKOXV+6wA:0
DEBUG: Code 233 at MPGelGPKmFfg80GVzB1MVlM7:0
DEBUG: Code 233 at pmoUlzam0PKt7F0lxsO27ZDM:0
DEBUG: Code 233 at ux6TdX6+EW33Sfl+jhwthMWg:0
DEBUG: Code 233 at e8P9Qu81DPFzS9vqNquScJT2:0
DEBUG: Code 233 at Z5wzm9KFw5wIUv4UmDJlrbUZ:0
DEBUG: Code 233 at TsskPxo3FQJ38amKk0/T+FT8:0
DEBUG: Code 233 at JePehWVAbXf19cT4YYop3UCj:0
Operation successfully completed
*** OOPS (The target drive is a WD Red NAS WD30EFRX 68EUZN0 3TB. Its write benchmark is 84 MB/s)
Note: this comes as a bit of a surprise. The maximum transfer rate I'm seeing (so far) is [6.0X] or 26.1 M/s. And, with 32 GB of DDR4-3200 memory, there's plenty of room for buffering data. Oh, well. I'll try again with my fastest drive. See below.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Program reads data faster than it can write to disk, consider upgrading your hard drive if you see many of these messages.
Error 'OS error - {Device Timeout} The specified I/O operation on hs was not completed before the time-out period expired' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '33080340480'
Error 'OS error - {Device Timeout} The specified I/O operation on hs was not completed before the time-out period expired' occurred while reading '\Device\CdRom0' at offset '33080340480'
DEBUG: Code 3221225653 at \zlO<XK'!<p!d<l/E":29395149
*** Trying again to my fastest drive. It can write at 5GB/s (Samsung 980 PRO PCIe 4.0).
This was looking good until about half way into the process. It was transferring at around 25 M/s [6.0X]. It's now at around 100 K/s [0.0X] [SAFE]. I don't see any error or warning messages.
Note: I did check the Samsung drive's temperature. It's fine.
*** Trying again to an older SSD (Toshiba OCZ TR150 480 GB). This benchmarks at 524 MB/s.
Error 'OS error - {Device Timeout} The specified I/O operation on hs was not completed before the time-out period expired' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '33048883200'
Error 'Internal error - Operation result is incorrect (78)' occurred while reading '\Device\CdRom0' at offset '33048883200'
DEBUG: Code 117637198 at \zlO<XK'!<p!d<l/E":29395149
Error 'OS error - {Device Timeout} The specified I/O operation on hs was not completed before the time-out period expired' occurred while reading '\Device\CdRom0' at offset '33048883200'
DEBUG: Code 3221225653 at \zlO<XK'!<p!d<l/E":29395149
Error 'Internal error - Operation result is incorrect (78)' occurred while reading '\Device\CdRom0' at offset '33048883200'
DEBUG: Code 117637198 at \zlO<XK'!<p!d<l/E":29395149
Error 'OS error - {Device Timeout} The specified I/O operation on hs was not completed before the time-out period expired' occurred while reading '\Device\CdRom0' at offset '33048883200'
DEBUG: Code 3221225653 at \zlO<XK'!<p!d<l/E":29395149
Error 'OS error - {Device Timeout} The specified I/O operation on hs was not completed before the time-out period expired' occurred while reading '/BDMV/STREAM/00000.m2ts' at offset '33059960832'
*** Trying a different Ultra HD Blu-ray now
I found something short, around 2 minutes and 18 seconds. It appears to have worked. YAY!!
005011:0000 Operation successfully completed
005014:0000 Saving 1 titles into directory file://F:/Video/UHD_IMAX_FOB
AV sync issues in F:/Video/UHD_IMAX_FOB/title_t01.mkv
AV sync in 1,2,3 at 0:01:09.736 (2.333ms) : encountered overlapping frame, audio skew is +2.333ms
004047:0010 AV sync issue in stream 5 at 0:00:00 : Forced subtitles track #5 turned out to be empty and was removed from output file
005005:0080 1 titles saved
005036:0104 Copy complete. 1 titles saved.
SUCCESS!! I have confirmed using VLC that this is a 3840 x 2180 video, and it plays beautifully.
Note: Handbrake successfully processed this into a 1080p format m4v.
*** Trying a larger file (8004.6 M) on the same disc.
Read rate is 31.0 M/s [7.2X]
Note: this turned out to be a 1080p video.
*** Same disc. Source size is 18,315.2 M. Speed is 22.2 M/s [5.1X]
And, one more file that is around 21 GB.
SUCCESS!! These are 3840 x 2180, too.
*** Different disc. This file is 48,215 M
Failed at around 32.6 GB. Huge error log.
*** Different disc. Source size is 16,867.7 M
Success.
*** Different disc. Source size is 16,362.6 M
Success.
*** Different disc. Source size is 42.3 GB
Success!! Note: very likely single layer!!
This LG drive was purchased specifically for this purpose. And, much to my delight, it's working pretty well! It's also quiet, which is very nice. The other positive surprise is it's working well as an external drive. That was forced upon me because my new case has no optical storage option. The front of it has a 360mm radiator for an AIO Corsair water cooler. My seven (6 case, 1 CPU cooler) fan air cooling setup in my old Corsair case was way too insufficient to keep this small furnace 
of a CPU cool. With the CPU running full blast, I see over 300W+ actual at the wall plug. That's with the GTX 1080 idle. I hit the 100C throttle point with the air cooling. I now hit around 70 maximum. Note: the new case has *only*