One of the main purposes of spatial filtering is to limit the size of the data that the WFS server returns, because large amounts of data can take a long time to download and process. After downloading a smaller subset of data to MapInfo Pro, you can use a local query to obtain the exact subset of data you need.
MapInfo Pro sends spatial row filters with geometry to the server. If a server does not follow the OGC specification regarding coordinate order, then MapInfo Pro uses the overrides as discussed under Applying a Coordinate Order Override to Correct how Objects Display on the Map. When opening a table for the first time, MapInfo Pro uses any override that exists from the MIWFSServers.xml file for that server. If no Table XML file exists yet to retrieve an override from, then you can add the table override via the WFS Refresh Table command (as described under Applying a Coordinate Order Override to Correct how Objects Display on the Map).
When using a WFS 2.0 or 1.1.0 server, MapInfo Pro only supports the BBOX spatial filter (with WFS 1.0.0, it uses any filter). A WFS 2.0 or 1.1.0 server defines the types of GML (Geographic Markup Language) Geometry objects that it supports. That list is limited to a predefined subset of all GML Geometry types. The GML Geometry type that maps closest to MapInfo Pro's region (MultiSurface) and polyline (MultiCurve) object type are not part of this predefined list, so MapInfo Pro uses the BBOX spatial filter.
The BBOX filter is useful with complicated spatial queries, such as when you want all of the data that is within a region. For this query, you would pick the region and do a BBOX filter. This returns data that is outside of the region, but it is less data then everything that is outside the region. When this data is in MapInfo Pro, you would then do a query to get everything that is inside the region.
There are no limitations on WFS 2.0 and 1.1.0 for non-spatial row filters.