Ok, I understand now.
To be honest, unsure of the purpose of the variables in esp-camera.h, it is provided by Espressif and has functoned without issue for me in multiple projects up to this point. I assume it is setting up the pin definition structure for the OV2640 camera connector but leaving the actual pins null to be declared in the main code as there are multiple ESP32 camera variants, using different pin configurations. I set it to the pins for my ESP32 in the main code, like I have for multiple other projects I have in use, including one functioning in Blynk1.0 .
That is why I included the Espressif git link for their esp_camera.h header/driver file. It is provided directly by the maker of the chipset and has never given an issue in multiple different previous projects. There are only issues when anything involving Blynk2.0 are involved. I did not generate, alter or create this file at all, I add it into my own project for utilizing an OV2640 camera on an ESP32 chipset, as provided by the makers of the ESP32 chip (Espressif)