In Litchi, I don't believe there is any speed control, nor gimbal tilt control, nor waypoint actions, when you fly beyond RC signal range. So effectively, the only thing you can program, for waypoints beyond signal range, is the position and altitude of the drone, plus the POI focus. And even then, the POI focus is maintained only by yaw of the drone, not by gimbal pitch.
So I have found that the best way to run a video capture while beyond signal range, is to make sure the gimbal pitch is set correctly before you leave signal range. I generally set gimbal pitch to 15 deg down shortly after takeoff, which is a good compromise for capturing the horizon in the video, but still getting close to what the gimbal pitch should have been even if it were under control. Then I check the waypoints individually in my mission plan to be sure the desired pitch for each POI is between 0 to 35 deg or so, which is usually the case. Sometimes I'll need to vary the drone altitude in the plan in order get within that acceptable pitch range. Also, during the flight, you must remember to turn on video before you leave signal range.
I don't usually find the gimbal pitch workaround to be much of a problem. It's the lack of speed control that bothers me more. Optimally, I'd like to run at full cruise speed out to the target site, and then slow down to get good video, and then speed up to get back home with enough battery reserve. But that isn't possible when you fly beyond signal range. You get just one speed. So choosing a compromise speed is also a necessary ingredient for your mission planning. Don't go too slow, or you'll run out of battery. Don't go too fast, or you'll compromises your video unnecessarily.
