`mapData` is more expensive than it needs to be

[effectfully]

mapData is currently 2x more CPU-expensive than listData:

  "listData": {
    "cpu": {
      "arguments": 33852,
      "type": "constant_cost"
    },
    "memory": <...>
  },
  "mapData": {
    "cpu": {
      "arguments": 68246,
      "type": "constant_cost"
    },
    "memory": <...>
  },

While it is genuinely slower than listData, perhaps not by as much. I believe the reason why the numbers are the way they are is that geq used to be really slow for mapData but not for listData. This was fixed in #7323, so you should recost mapData.