@Charles Lewis yeah this is something I've messed around with a bit — the short answer is that tightening the connection interval at those ranges is doable but you have to be pretty careful about your supervision timeout ratio or you'll get spurious disconnects that are hard to diagnose.
The thing that bit me early on was that at longer range you're dealing with more variable propagation delay and occasional retransmissions, so if your supervision timeout isn't sitting at like 6-10x your connection interval minimum, the peripheral can timeout before it gets a chance to recover from a bad packet window. I'd rather have a slightly wider interval with a well-tuned timeout than a tight interval that's constantly on the edge.
What's your current interval and supervision timeout set to? That'd help narrow down whether there's actually headroom to tighten things or if you're already pushing it. Also worth checking the GitHub repo for the module firmware — there are some STM32WB07 specific timing considerations in there that aren't obvious from the BLE spec alone.
