I jumped into game development earlier this year because I too feel that there are plenty of business use cases for a game engine to power business intelligence

I jumped into game development earlier this year because I too feel that there are plenty of business use cases for a game engine to power business intelligence applications; especially in VR/AR. It was not only my first time doing 3D, but also my first time using a real IDE. Results have varied. The first thing I'll tell you is that the tooling for building enterprise apps is woefully inadequate out of the box. The things that come easiest to you, specifically CRUD app building, are much more difficult in a game engine. There are no native UI elements, no theming in the way we've come to expect, and the workflows are all completely different. I was used to building database connected backends, and switching to a state machine model really threw me for a loop. If you have experience building native apps, you're probably going to have a much better time than I did. As far as learning the interface, that's not so bad. Follow some of the tutorials and you'll be able to get up and running in no time. The rabbit hole for me was understanding WHY things were doing what they were doing, as opposed to figuring out how to do it. Except in those times which I COULDN'T do something natively that I was expecting to be able to do...which happens a lot. My recommendation is to set up the game engine of your choice, learn how to build to multiple targets, and then craft something you've already done elsewhere to see how you like it. Once you get that going, you should have a cursory understanding that will allow you to flex some creative muscle. Good luck!