The main idea and purpose of integration (which is also what was done) are to insert Toolset stuff into Elementor.
That means you'd create a View or Form or Content Template, then use the Elementor Widgets to insert them to an Elementor Template or single Post.
This is as well because Elementor is a front-end editor and that doesn't allow to edit Content Templates, for example, this is why there is no such feature as there is for example in/with Beaver Builder or DIVI (where you can edit CT's)
Now, this is also what was tested, and we did not dig into other, unintended possible ways to use it.
What we know is, for example, if you assign an Elementor Template AND a Content Template to the same content... you end up with a nice mess where nothing is displayed anymore at all.
https://toolset.com/forums/topic/view-issue/
https://toolset.com/forums/topic/single-templates-in-elementor-not-showing-content-after-last-toolset-update/
https://toolset.com/forums/topic/generatepress-elementor-shortcodes-not-displaying-anymore/
https://toolset.com/forums/topic/some-custom-post-types-not-showing-elementor-sitewide-header-template
etc
And, of course, the erratum we first communicated in with each other:
https://toolset.com/errata/elementor-pro-template-shortcode-not-rendered-in-view-loop-item/
Will this sort of things work, will it proceed to work?
Well, it works now, if you do it like described in the Erratum.
We will surely not break that on purpose. What we face here is likely a run between filters on the content.
So, everyone, Elementor, Views, tries to filter the content and substitute it with their templates or contents.
Sometimes A wins, Sometimes B wins. That is sometimes fixable, sometimes it needs a workaround.
If you start nesting such templates, and hence it's filters, it gets worse. So I do not reccomend to nest too many items, or, none at all if possible.
It makes it difficult of course to provide proper integration, however, since we would be racing constantly between 2 things wanting to do the same, at the same moment, on the same content.
That is why I cannot say, yes do it and we will ensure that this keeps working because it is not the officially intended way, but also, there is no reason for us to go and break this on purpose.
And as you see, we do our best to solve it or at least work around it, and that, we will also proceed to do in future.
Hence you are relatively safe using it, however, must be aware that you are using a "not official" method.
The Official Method until now is to insert Toolset Things into Elementor, using the Widgets.
We might, however, consider this as a fully inbuilt feature in future, of course. This depends on a lot of things, but you can make your voice heard here AND at Elementor, mentioning how much you wish for more cooperation and integration.
This will move both side's developers towards the right directions.
I will take care of letting our Developers know about this need to design Views with Elementor.
As for Toolset Forms, here I see less chance and filed a request so you can upvote it (and others) since this is absolutely impossible right now and requires a totally new integration method.
https://toolset.com/feature-request/style-toolset-forms-with-elementor/
https://toolset.com/feature-request/?wpv_post_search=elementor&wpv_view_count=686737&wpv_sort_orderby=post_date&wpv_sort_orderby_as=string
