Do you mean something like this?
**broken link removed**
Pan-tilt is something you have to build yourself (for any camera in general, not just this one), let alone any yaw-pitch and roll data and time stamping. You would have to build the pan-tilt mount yourself and mount the camera on it. And for the orientation data you would also have to come up with something yourself. Why? Because a camera with any one of those things (except for time stamping) was made for UAVs, which probably means it was made for military...commercial if you're lucky. But either way, far beyond the cost of what a single person can afford.
Cameras that record their own yaw/pitch/roll are for localization and have internal IMUs. Considering the cost of an IMU is $2000+ for the cheapest ones (with most being $5000+) it's probably much more when built into a camera. Plus it's also heavy and a bit short-sighted to dedicate so many resources to such a menial task. I've never seen a camera with a built-in IMU to determine it's own orientation. It's expensive, redundant, heavy, and a waste of such an impressive piece of hardware. (An exception is stabilized cameras, but those just have gyros and aren't IMUs because they don't require absolute accuracy for long periods of time.)
It makes far more sense to use a single IMU to track the plane's orientation, and use that with the servo position feedback to figure out the camera's absolute orientation. THat's super easy to do...you need are some servos, a microcontroller, and an IMU (assuming you don't need to build the IMU). Your biggest problem is getting an IMU.
TIme-stamping is easy if the camera doesn't have it. If it's real-time video...no problem! If it's photographs, just make a circuit that records the time every time you click the shutter button. Then correlate the photos with the time afterwards since the camera should be storing them in order. But we're all lazy here and that takes some work.
Do you actually need to know when the photos were taken? Or do you just need to know that they were taken at the same time between cameras? THere's a real simple solution to that. Just use the same shutter signal for all cameras. Since the photos are stored in order it's very easy to know which photos were taken at the same time between the cameras.
But if you're building camera orientation+IMU feedback electronics, might as well add on time stamping since it's dead easy. A single MCU should be able to take the readings from an single IMU, and all the pan-tilt servo positions from multiple cameras and figure out all their orientations all at once every time the shutter is used. And since RC servos give no external position feedback, the only way to get it is to measure the position PWM signal. So the MCU might as well be the one sending those signal anyways. Then it could ensure the cameras are always pointing at a fixed angle relative to the ground (at least as much as the mechanics of the pan-tilt will allow).
There are so many things you could do.
1. THe cameras could be maintained at a fixed angle relative to the ground in which case you probably assume the cameras are always at X degrees relative to the ground in which case you don't need to read out the camera orientation feedback (if you are willing to assume the control loop is sound.) Only the control loops needs this info which saves on a lot of work with the interface.
2. Or you could take the more boring approaches like being able to change the camera's position in flight relative to the plane (not the ground) and the camera spits out it's own orientation data.
3. Or something like 1, except that you can adjust the angle that the cameras maintain relative to the ground in-flight. THen you'd need to somehow record what photo corresponded to which angle hold setting. But seems more like a gimmick to me unless you had a very good interface built. Because then it'd just become a pain in the ass to be setting the angle hold setting of multiple cameras in flight.
Cool stuff.