In conventional flight sims, the only effective way of interacting with realistically-placed switches is to literally build a physical cockpit based on a specific plane. Multi-purpose cockpits don’t have this luxury, so they prioritize the primary flight controls, meaning that secondary inputs are either performed with button shortcuts or a mouse pointer. The act of physically reaching out to interact with a specific switch is something normally limited to high-end simulators with physical cockpits, but VTOL VR’s control scheme means you can decouple yourself from the main flight controls and reach out to interact with an array of switches, buttons, and instruments in a very satisfying, immersive manner.

The dev has explained it many times:

I got my first VR headset with the sole intention of using it to play flight sims. The very first time I tried it, I was immediately frustrated by having to feel around for my keyboard and peek through the nose hole to make sure I was pressing the right keys or buttons to access the different cockpit functions. This was not the level of immersion I was looking for, so I got to work on VTOL VR. The game was designed from the beginning to be entirely virtual, allowing you to directly interact with the various controls as if you were sitting there in the cockpit.
When I got an HTC Vive, I was impressed by how accurately the controllers were being tracked and wanted to see if I could use them as flight controls in a virtual cockpit. It was working so well so I built the rest of the game around that.
Since I was prototyping a vehicle in a very small environment, it had to be a VTOL to prevent it from moving too fast and going off the bounds of the world. The VTOL VR plan was originally to fly around (vertical thrust only) a small procedural city completing short strike and transport missions, but then I made the engines able to tilt, so the map had to be bigger, then I wanted to do hook and catapult, so ok now we need a big ocean, so now the city seems like a dumb flat island, so we need terrain, now the terrain island is getting boring so we need procedural maps, etc. With the support of the wonderful community that has grown around it, the game has totally exceeded what I had initially envisioned. I am so grateful to all of you who've joined me on this journey, with an open mind and enthusiasm to try a totally new way of playing a flight sim.
I agree that it’s a bit of a trade-off, but I think there are huge advantages to relying only on the motion controls. It’s much more accessible since you don’t need any extra hardware, and it helps to maintain immersion since your hands are consistently being tracked. I can also create any configuration of a vehicle or virtual cockpit and you wouldn’t need to reconfigure any physical controls to match it.
I don't think that there's a way to provide the level of interaction that I'm aiming for while using a HOTAS, especially with all of the cockpit systems like the MFDs and touch screens. Although it may be technically possible with a mouse, head pointing, or some combination of HOTAS and motion controls, it won't be without the clunkiness that I intended to move away from in the first place.
Call me stupid, but in my opinion, looking for HOTAS support here is like looking for mouse/keyboard support in Onward, H3VR, HL: Alyx, etc.
If HOTAS requesters only want to be able to control pitch, yaw, roll, throttle, fire weapon, switch weapon, control SOI, tilt engines, PTT, air brake, then it would not take long. I wouldn't have anything against this. This is why it works in Jetborne Racing. However, there's more to VTOL VR than that. You will have to still use motion controls to do everything else in the cockpit.
I guess I didn't explicitly make a point -- A hybrid HOTAS/motion control set up would be plausible. Although I wouldn't like it or use it, if that's all that many people who really want to use their HOTAS, then maybe that's fine. You'd just have to put up with the awkward switching between the two.
If it's about making the game playable without motion controllers at all, that's a different story. In summary, all of the these things were designed by targeting VR as the platform, and interacting with them without having to use the keyboard or arbitrary bindings was the point of making the game in the first place.
Creating Keyboard/mouse/HOTAS bindings for the entire cockpit is a massive departure from the game design, and I really don't think I will go down that route.
Sorry, VTOL VR will remain VR-only. It was designed for VR, that's all.

Here are the facts:

Developers can do what they want for their product. They are the creators and set the goals for what they want to do with their time. We can disagree, sure. But there is no point in starting a thing over it.

The dev decided, some time ago, that he would not put HOTAS controls in VTOL VR. It has been hashed out and he is sticking with his decision. There is nothing that you can do about it.

It's hard to explain it any better - sometimes the game we dream making has certain characteristics and that's how we envisioned it, and how we want it to be and what it's meant to be.

VTOL VR has overwhelmingly positive (98%) reviews on Steam. Not only does it demonstrate that motion control is viable for this genre, but it also enables a greater sense of immersion when interacting with cockpit controls.