Since Sentinel is only ever consulted when needing to determine where to connect to, and you are apparently not using sentinel in in-band or client code, then Sentinel "performance" is unlikely to be the cause.
You'll need to examine the sentinel logs to see if you changing the config is resulting in sentinel trying to fix it for you and possibly causing twemproxy restarts (since it does not yet support hot reload) which could in theory be causing delays. But you've not posted enough details on your setup and conditions to do much more than guess at this point.