Do developers require an activity for efficiently viewing datatable values in a tabular format?

Continuing the discussion from Datatable Visualizer Activity - Proof Of Concept?:

Now, my concern is whether it’s worthwhile to develop this table UI activity for developers to visualize datatable data.

If the answer is yes: Since the activity aims to provide a quick view of the datatable, what do you think should be the maximum number of rows and columns displayed in the table? If there are millions of rows, do developers typically look for that level of specificity? I ask this because if I can set a maximum row and column count that the activity supports, I can optimize it to display the view quickly and effectively.

If the answer is no: Could you please suggest alternative ideas or modifications that can be considered?