No, not without using filters to insert raw SQL, you can do comparisons, such as greater than, smaller than, but not ranges, but even then this will be an incredibly slow query, doing it is a bad idea:
- post meta tables are optimised for finding meta when it already knows the post ID
- taxonomy tables were built for situations where you’re searching for posts that have data that’s already known. This is because searching post meta for posts is excruciatingly slow
- Adding a math operation prevents the database from using Indexes, forcing a table scan where it has to test each and every row to build a temporary table that the final query can be ran on
You’re running head first into a tradeoff between speed and accuracy unawares, and have chosen perfect accuracy, not realising the sacrifice of speed can be extreme, and grows ever larger as the amount of post meta increases
Instead, use a taxonomy and auto-assign terms for common price ranges, and use those to filter by. That way you can still store the exact price in post meta, but you’ve got a much faster way to search for things by price. Additionally, the UI becomes simpler to implement