You do not have to remove these as they will not be visible to end users unless you actually use them to create pages for an object. They also have to be present for the Community Builder to work correctly as templates for the object pages.
When logged in as a community user if I try to navigate to an object by URL hacking I'd just get an 'invalid page' error, e.g. hacking the URL from https://.force.com//s/ to https://.force.com//s/Account/Recent will give an invalid page.
To enforce access to records for community users you need to enable the External Sharing from the Sharing Settings page and make objects Private, then use configuration to control which records on an object they will have access to.
The record access is different for users on Customer Community and Customer Community login where you need to use Sharing sets to make records visible and Customer Community Plus or Parter Community users where you can use Apex sharing or normal SF Sharing settings to share specific records to the community users. For example only allow the community user to see the account record that is linked to their Contact record, only allow community user to see their own contact record.
With the list views it is not possible to prevent a community user viewing the 'Recent' record list but this will only have data in it once they have viewed some records and the others can be restricted to internal users (though that has to be done in Classic not Lighting view).