There are a couple of suggestions that I can see:
1. The datastore is not intended to be the be-all, end-all data storage solution. As you can see, it has its' strengths and weaknesses. In your case, I recommend using Cloud SQL.
2. If you absolutely insist on using the datastore, let me ask a question: are the time ranges that you're using highly standardized? For instance instead of expressing times can you express availability as morning/middle-of-day/afternoon/evening? So instead of doing queries that are number based you can do boolean equality searches (example: search all equipment entities that have the property tuesday_morning_available and wednesday_afternoon_available set to true).
3. Use TextSearch as Julie and Moises have already suggested.
4. As Julie suggested, query using one inequality, then filter on the remaining equality within your code.
5. If you have a small dataset, you can implement a small DB engine entirely in memory within a backend. It's not as reliable as using the datastore, but it can be faster if you implement it correctly.
-----------------
-Vinny P
Technology & Media Advisor
Chicago, IL