Since the smallest bInterval for full speed is 1 ms, 2 ms round trip is about as fast as you can expect. bInterval defines only the reserved bandwidth at the host controller. If the host system is busy, the delay for a host application to read the data and respond might be longer. So you shouldn't assume a response in 2 ms.
With high speed and SuperSpeed, interrrupt endpoints can request a shorter bInterval. However, to comply with the specs, interrupt endpoints in the default interface must have wMaxPacketsize <= 64 bytes, and HID drivers in major OSes don't support selecting alternate interfaces. A custom driver could do so, but if the bandwidth isn't available, the driver can't select a greater bandwidth. And you'll still have the somewhat unpredictable system delay in reading the data and sending the response.
Jan