The standard many-to-many, with a defined through-table, does not support that.
What you can do is split the relation into two one-to-many relations, by using a model for the through-table. You can use that in parallel to the current many-to-many, if you don't need the data in the through-table, you can still use the current relation.
and get all films in cinema 1, including all time info (assuming that the relation to the pivot table is called 'viewing', and the relation from that table to the films table is called 'film').
Note that if you take this route, give the pivot table an id column.
Don't use the combination of 'film_id' and 'cinema_id' as a compound primary key, the ORM does not support columns that are both primary key and foreign key at the same time, you'll get into a constraint deadlock when you try to delete a cinema or a film.
You can name the model anything you like, just use the _table_name property to define the correct table if the Model can not determine it from the model name automatically.