I can see the problem with that page where the View is reported as missing etc., but I can't account for why it would have happened, and—more importantly—I can't see how to fix it. I tried something I thought might work, but it didn't, and I don't have any other ideas. (With the switch to Gutenberg the WordPress editor has become very complex to debug.)
If you are not able to revert to a working version from a backup then I don't have any other suggestion that to delete (not just trash) the current search page and start over.
Also go to Toolset > Views and delete the View in question (Airports, with ID of 1125), as well as the extra View you added to the same page.
Start again with a new search page and a new View and new Map. Take a backup in case you need to revert to this point again.
As for the custom fields, for the map to work, or even without a map, to be able to search for posts by distance, you must have an address field (by which I mean a field of the type address, not some text field called address).
When you use Relevanssi you can combine filters. So you can have a text search as well as apply some other taxonomy or custom field filters at the same time. But! The distance filter is a special case that requires special handling internally, and I can't say for sure without trying whether the distance filter and Relevanssi-based text search will work properly together. I will try on a test site to see if I can confirm it should work.
One thing to clarify with adding Relevanssi: it only applies to text searches, even when you use it to include support for searching custom field values.
So it doesn't necessarily make sense to add all custom fields to the Relevanssi index. It only makes sense to add custom fields whose values you want to be found in text searches.
Say you had a custom field for, I don't know, height about sea level, in feet. It could be that you wanted to include a filter for height above sea level in your View, so that users could say to only show results above 5000 feet. But you almost certainly wouldn't expect users to enter a text search to find the text "5000" from the field.
And if you were to add this field to the Relevanssi index then you would just be clogging up (and slowing down) the Relevanssi index.
I'll report back on what my test shows about trying to combine Relevanssi text search and distance filtering.