Hi Derrick
There a few points to grasp here.
Firstly, it is important to understand how the different parts of the page are generated.
WordPress pages are generated in blocks: the header, including the site navigation, the footer, one or more sidebars, and then the content itself. When viewing a single post the content is that single post. If you view an archive page (e.g. the blog, which is a list of standard posts, or an archive of a custom post type, or a category or author archive, etc.) then the content area is the list of posts.
You can see a visual representation of this here: https://toolset.com/documentation/user-guides/view-templates/#attachment_183885
If you use Types to create custom post types with associated custom fields and taxonomies and do nothing else, then your single custom posts and archive of posts will be output according to your theme's PHP templates, just like standard posts.
That means they won't output any of your custom taxonomies or custom fields, and the design will match that of regular blog posts (e.g. it may have a prominent featured image).
Which is where Views comes in, allowing you to create Content Templates for your custom post types so that you can design the output to include your custom fields and taxonomies according to your needs, and only including elements such as the featured image if you want to.
You can also customise the archive of your custom post types, or create custom searches for them.
But all this still only affects the content area of the page.
Many themes will have different page layouts (e.g. you can choose whether or not to have sidebars or full-width page layout), but Views will only affect the content area of the page, whatever your theme determines that to be.
So the next step is Layouts. If it is integrated with your theme then it gives you complete control over the whole page layout, and not just the content area. So instead of the header, footer, and sidebars coming from your theme, you create them in Layouts, and can assign different designs to different pages (e.g. use a different headers to your home page, to your blog, and to one of your custom post types).
That's how the pieces fit together. As a rule of thumb I normally suggest you start with Types and Views in combination with your theme and the customisations it allows, and if you envisage scenarios where that will not give you sufficient control over the page design, then add Layouts to the mix.
There is no substitute to working through some of the documentation, to see how to create Content Templates, for example, which is described in the link I shared above, for example.
You can read more about Layouts theme integration here: https://toolset.com/documentation/user-guides/layouts-theme-integration/
Note that the next major release of Layouts will work with themes that have not been integrated, but it will only be possible to design the content area with them.