iRule tp detect HTTP and TCP requests and then do some magic.

In addition to what Stanislas said, also note that with your existing iRule, you are using http commands and events which means that you have an http profile on your Virtual Server. What the profile does is it makes the BIG-IP parse http headers, which means that the traffic must conform to some base minimum of the http standard. That in turn means that traffic that isn't http going through that Virtual Server will fail, since the BIG-IP will drop non-http traffic. So it's unlikely that you will be able to handle both types of traffic on the same Virtual Server.

Supposedly there's a way around that by creating a http profile that uses transparent as the proxy type, but I haven't played around too much with that so I'm not sure how well that actually works.