What is 192.168.x.250? Does that lie beyond your firewall?
You have a static route stating that if a packing is coming from (anyIP, any subnet) send it to 192.168.x.250. Static routes have a cost of 1 which means they are taken prior to any dynamic, or learned routing.
So, if 10.x.100.1 is trying to get to 192.168.x.254, it would first need to hit 192.168.x.250. Is 192.168.x.250 between your switch and 192.168.x.254?
I believe your switch is capable of basic routing based on the fact you have "ip route" command in there. Take a look at your routing tables with the command "show ip route".
It's been a while since I worked on Cisco (I truely miss it - Avaya blows but this new code I got today seems better) and I don't know how your network is set up in full, but I hope this helps.
Edit: If you are capable of static routing, you can run a lot of static routes for a network. The question would be, would a strict routing table be the right choice for your network? If you only have a few subnets, it really wouldn't matter. If you plan on getting a bigger network, then I would look into getting a routing protocol for your network. Each protocol scales differently and depends on your network. This is about as basic of an answer as I can give because it really depends on your network.
When you explain packet loss I think a bad cable SOMEWHERE on the path (including media converters), an overburdened CPU (on some device on the network like a firewall, router, switch, concentrator, multiplexer, etc), or a split horizon. Unless your code is buggy like early Avaya ERS 4500 software versions... ugh... I wouldn't think that Cisco would be buggy.
Please, let me know if you need help or if this answers your question. I wouldn't mind brushing up on my Cisco configurations.