Official comment

1. We will look into the work mode error. Was it possibly in video mode before that?
2 and 3. We will look at these.
4. That number is based on the exposure time and the air speed. If you have a long exposure time and a fast speed that number will be large. It could just be that you were flying over a dark area and the camera was trying to compensate but lengthening the exposure time.
5. If you change the state of that switch it will stop the virtual stick controls. If nothing else happens it will return home on its own or you can take over manually.
6. We do a lot of our development using the simulator so it should behave pretty well. That video is, um, weird. If you turn on the Force Virtual Stick setting at the bottom of the Settings it will show you the target point as it flies. The issue might be that you are flying pretty low with pretty high overlap (80%). This places the passes pretty close together and might be something we need to work on.
Based on how long it took to calculate the terrain profile you might want to look into getting a faster iOS device. We have been recommending the use of at least an A10 processor or better for a few years now. That requirement will likely be creeping up soon.