As per the usual definition of a View for MVC architecture, it is anything capable of interacting with the user on a visual level.
Quote from medium.com says the following:
The Controller’s minions, generic reusable interface objects that the Controller is using to do its job. Ultimately, how the model is displayed on screen. Most of the objects in the view (Buttons, Sliders, text)
So essentially, any part of the Swing library which has a Visibility attribute is considered a View. You mentioned VM for JTextField, but it is actually the essential relation between a Controller and a View in this architecture, where you have an empty View, which you populate and present to the user by "throwing" data at it from the Controller.
As for the compound View, I'd say it depends how you look at it. It's essentially a mix of different Views which may or may not present one logical group. But technically speaking, I wouldn't really put those 2 in the same category.