How to isolate active record in laravel5?

Question

Laravel

I wondered how to safely isolate AR models and drive them around the application, through services, return them from repositories, etc. ?
Recently, I realized how not much messed up with the architecture of the application. The fact is that I sprayed AR models throughout the project, despite the fact that I used the repositories (as it turned out to be wrong).
For example, we have a simple code:
$types = Type::with('fields')->get();
We take some types from the store. Suppose now it is AR, and tomorrow it is REST API or Query Builder, in general, the result will be different. Ie in the first case AR, on the second an array, in the third a collection. Not good.
I would like to bring this whole thing to one format and:
- do not be afraid that someone will intentionally or accidentally make $type->save() anywhere in the project
- return a single data type from the repository
- get away from AR logic, and transfer just data to views and between services (like through DTO)
Collections come to the rescue:

$type = Type::findOrFail($id);
        collect($type);

With one entity, this works well, but when there are, say, relations:

$types = Type::with('fields')->get();
collect($types->toArray());

It turns out that all nested relations are just an array, that is, not every entry in the relation is a collection, but something like this:

Illuminate\Support\Collection Object
(
    [items:protected] => Array
        (
            [0] => Array
                (
                    [id] => 1
                    [alias] => test1
                    [name] => Новости
                    [description] =>   
                    [fields] => Array
                        (
                            [0] => Array
                                (
                                    [id] => 1
                                    [type_id] => 1
                                    [type] => test
                                    [is_required] => 1
                                    [validation] => 1
                                )

                        )

                )

            [1] => Array
                (
                    [id] => 2
                    [alias] => test2
                    [name] => Статьи
                    [description] =>   
                    [fields] => Array
                        (
                            [0] => Array
                                (
                                    [id] => 2
                                    [type_id] => 2
                                    [type] => test
                                    [is_required] => 1
                                    [validation] => 2
                                )

                        )

                )

            [2] => Array
                (
                    [id] => 3
                    [alias] => test3
                    [name] => Вакансии
                    [description] =>  
                    [fields] => Array
                        (
                        )

                )

        )

)

That is, records inside the fields relation, just an array, not a nested collection.
Interested in the following 2 questions:
- Is it right to get confused with AR isolation using DOT or collections?
- Do I need to write my own collection handler that will convert a model with relations recursively into a collection with nested collections, or is there another option?

Answer 1

www.martinfowler.com/eaaCatalog/rowDataGateway.html

Answer 2

We take certain types from storage. Suppose now it is AR, and tomorrow it is REST API or Query Builder, in general, the result will be different. Ie in the first case AR, on the second an array, in the third a collection. Not good.

Create a service layer, write incoming and returning types (you can create new non-persistent model types) in methods. And the implementation inside the service can change, it will not affect anyone.

not afraid that someone will intentionally or accidentally do $type->save() anywhere in the project

Why? AR is so used.
The question looks like you just want to wrap around AR by creating a self-made likeness of DM, but why don't you just take DM right away?

Is it right to get confused with AR insulation

This (anti)pattern was created and popular during rapid development, initially breaking SOLID. They usually do not bother with him, but rivet small projects.