There are several issues at hand; some in iTunes and some in iOS 11.x ... both on macOS and Windows. Also note that some older operating systems may not support ID3v2.4 (ex: Windows 7) without 3rd party shell integration add-ons for Explorer and/or Windows Media Player. The same is likely true on older macOS (ex: El Capitan).
Using iTunes Library to Copy to iOS Device:
As of iTunes 12.7, ID3Tag v2.4 is supported. iTunes sets the "Work" ID3 tag equal to the "Grouping" tag. As previously mentioned in this thread, problems arise if the classical music tag details are partially filled in. This can be remedied by ensuring that the "Grouping" ID3Tag is empty.
iTunes expects files to be added to the Library via the "Automatically Add To iTunes" folder; during the add/import process, iTunes renames the files (ex: ## song name.mp3). Songs with the "Compilation" ID3Tag are placed in the "Compilations" folder. Artist/Album folders are initially determined by the "Album Artist" ID3Tag.
Copying the songs from the iTunes Library to the iOS 11.x device yields expected results.
Using iTunes to Copy to iOS Device (i.e. Not Using iTunes Library):
Copying the songs from the iTunes Library to the iOS 11.x device yields songs that appear as their own separate albums.
Removing the songs from the iOS device and recopying yields expected results providing that the ID3Tag information is correctly entered and "Grouping" ID3Tag is empty.
The reason is it works the second time around is that the Music SQLite database on the iOS device contains a list of all songs that have been copied to the device ... even when the song is removed. This can be seen by used a tool (ex: iMazing) to copy the SQLite database locally to a computer and using an SQLite DB Viewer to examine the tables.
Using a 3rd Party Application to Copy to iOS Device:
Using a 3rd Party Application to directly copy the songs to the iOS device yields the expected results regardless if the ID3Tags are properly set or not.
At first guess; it leaves me wondering if perhaps a further iOS update will be required as the problem persists on iOS 11.4.1.
Cheers,