EDIT
I missed the actual question here, it is perfectly save to change post
to a custom post type. Just make sure to assign the build in taxonomies to the custom post type if you need them and if you already have some kind of hierarchy build through them.
Also make sure that you properly register your post type to suite your exact needs
ORIGINAL ANSWER
I’m not sure how you would want to have your setup to look like, but from what I read, you can actually do the following
-
Create a non-hierarchical post type and simply change your posts to this new post type. Custom post types are excluded from the main query (except on taxonomy and custom post type archive pages (which you can “switch off”)) and menus. You can use
pre_get_posts
if you need to add custom post type posts to some archive.You can also assign custom taxonomies to them (or even the build in taxonomies
category
,post_tag
andpost_format
) and have them work exactly like normal posts. Changingpost
topage
have other issues that you don’t need, as pages have its own methods how it works and how it is dished up in front end. Also, as I previously described in another answer to one of your questions,page
does not have taxonomie and are not meant to have taxonomies. -
Set a static front page.
-
Set a custom tag or category to the posts and use
pre_get_posts
to exclude them from the loop. -
Simply remove the loop from the homepage if you do ot need it. This will however have the drawback that pagination will still work, so you would need to remove this as well