Better option would still to get fairly deep into the technical underpinnings of your org’s platform, and be the guy who can bridge both sides — deep understand

Better option would still to get fairly deep into the technical underpinnings of your org’s platform, and be the guy who can bridge both sides — deep understanding of the business, and one of the few understanding of the tech stack that enables it. That’s probably the best place to aim. Few people in your org will accomplish that successfully, so being the one who can will set you apart, help get things done faster (help developers gain domain context, help the business understand how things work under the hood), and keep yourself relevant and useful.