I have had some time to explore Virtual Dub2 as suggested by the links and use the project files posted by optodata. Using PD17 with the addition to the profile.ini. Here is what I found:
1. The original Drone.mp4 can be edited in PD17 and Produced at the default h.265 3840 x 2160 37 Mbps profile with svrt active.
2. Use Virtual Dub2. Open the edited Drone.mp4. Load the 5148x2160 1.33 desqueeze.vdproject. Save as Drone1.mp4. Mediainfo reports AVC 38.4 Mb/s, 5148 x 2160, AR 2.40:1, 29.97 fps (constant). This is essentially the same parameters as the original but horizontally expanded by 1.33. This displays in all media players tested. Import to PD17 and see a wide blank black preview screen while playing. No error messages occur.
3. If using PD17 you can stop now as you can edit, produce with svrt, and use Virtual Dub2 in step 2 above to get the 2.4 AR video desired..Mission accomplished.
4. Loaded Drone and Drone1 in the PD17 timeline. Produced with the custom 2bskyhi intermediate profile. The Drone1 portion is a blank black and the Drone portion display as HEVC 5148 x 2880, AR 16:9, 26.2 Mbps, 29.97 fps (variable). Produced Drone_0.mp4.
5. Use Virtual Dub2. Load the 5148x2160 Post PD.vdproject. Open the Drone_0.mp4 produced by PD17. Click Save. The new Drone_0.mp4 output file is AVC. 12.5 Mbps, 5148 x 2160, AR 2.40:1, 29.97 fps (constant). Again the blank black portion and then the correct expanded video is seen. Mission accomplished for PD18 users.
When I get the chance, I will explore Virtual Dub2 more and change the parameters to 5184 instead of 5148 for the horizontal resolution which gives me some incentive. It is possible that PD365 users can also use SVRT like in PD17 if they update to the latest patch announced. Thank you optodata for all your hard work. You made it so easy for me to use Virtual Dub2.
EDIT: Maybe PD18 users need only to perform the first two steps above if they get the error on step 3.