I didn’t understand how the exif stripping works in Android in the past, but apparently it’s the storage access framework enforcing permissions (ACCESS_MEDIA_LOCATION) and stripping the info if the share destination / receiving target doesn’t have the permission. There’s more knowledge linked in this nextcloud/android issue.
OpenCamera can obviously record the geo data, so it’s up to the bluetooth share. As you do not want to pull files through adb and a cable… when testing a photo with exif data, picking a file through localsend (picking, not sharing to) I got the file wirelessly and exif untouched, same md5 hash.