I would define a tile as a slice of geometries, not whole features.

The difference with Tileless' approach, is that they load whole features from the database and don't split them into tiles. So if a feature extends outside the current view, they would load the whole geometry rather than the intersection of the tile's extent and the geometry.

Vector tiles are optimized for concurrent downloads and browser / CDN caching and doing a good job of that.