First, thank you for responding to my post so quickly. It is very much appreciated. Second, an OpenCore developer solved the problem for me and it is a VERY simple fix. He knew about your firmware and the changes it has undergone in the past year. If you have any macOS users that have questions about using your firmware with macOS, feel free to have them contact me on the Insanelymac forum. I have the same username on that forum as this one.
I will tell you the fix but I doubt it will mean anything to you but, for the person that had the same problem as me, it will fix it. In the Opencore config.plist, go to UEFI→Quirks and, for the setting “Disable security policy” change it from No to Yes. That’s all it takes. Apparently, disabling secure boot and secure boot model aren’t enough and this also needs to be used, although the default setting for it is No. The developer’s exact words to me were “disablesecuritypolicy=true under uefi/quirks if it is for any of the recent mrchromebox firmwares.” Feel free to pass it on if the occasion arises.